Skip to main content

Blockchain-Specific FAQ

Applies to Zelcore 8.39

Written for Zelcore 8.39.0 (October 2026). Where an answer names an earlier version, it says so.

Kadena (KDA) Questions​

Kadena status (October 2026)

Kadena LLC ended its business operations on 21 October 2025. The blockchain kept running. On 8 November 2025 the network moved to Kadena Community Edition, a community-run continuation, and it is still producing blocks. Your addresses, keys and balances did not change. Several exchanges removed KDA trading after the shutdown, so check that your exchange still supports KDA before you deposit. Sources: Kadena Community Edition, Decrypt, 22 Oct 2025.

What is Kadena's multi-chain architecture and why does it matter?​

Answer:

Kadena is one network made of 20 parallel chains (Chain 0 to Chain 19). Each chain has its own balances. It is the same KDA on every chain, and your account name is the same on all of them, but the balance on each chain is separate. Moving KDA between chains takes a cross-chain transfer.

Related:

Which Kadena chain should I use?​

Answer:

Use the chain where your KDA is, or the chain your recipient or exchange asks for. No chain is worth more than another. Zelcore opens on Chain 0 until you choose another chain in the Chain ID selector.

Related:

How do I know which Kadena chain my KDA is on?​

Answer:

Open Kadena (KDA) in Zelcore and open the Chain ID selector. It shows the KDA balance of each chain. You can also look up a transaction hash on the Kadena Community Edition explorer.

Related:

What does "ERR_BAD_REQUEST" mean when sending KDA?​

Answer:

The Kadena service rejected the transaction. The usual causes are no KDA on the chain you send from, not enough KDA left for the fee, a wrong account, a receiver that does not exist on the destination chain yet, or a temporary service problem. Check the chain in the Chain ID selector, leave some KDA for the fee, copy the account again (it should start with k:), update Zelcore and try again.

Related:

How do I send KDA to an exchange?​

Answer:

Check the exchange's KDA deposit page first: several exchanges removed KDA after October 2025. Follow its network and chain instructions, move your KDA to that chain with a cross-chain transfer if needed, then send to the deposit account. If the exchange does not name a chain, ask its support before you send.

Related:

How do I move KDA between different chains (cross-chain transfer)?​

Answer:

In Zelcore, choose the chain your KDA is on in the Chain ID selector, open Send, enter your own k: account and set Destination Chain ID to the chain you want. The transfer takes up to about 4 minutes. Keep Zelcore open. If it does not finish, use Finish Cross Chain Transfer on the Kadena screen.

Related:

What is a "legacy address" in Kadena and why does it matter?​

Answer:

Zelcore gives each key two Kadena accounts: a k: account and a legacy account that is just your bare public key. Use the k: account. It is the standard Kadena account, and Zelcore warns you when a legacy account on a chain is not controlled by your key.

Related:

Why isn't my KDA showing in Zelcore even though I see it on the blockchain explorer?​

Answer:

The KDA is usually on a different chain or account than the one Zelcore is showing. Check every chain in the Chain ID selector and both accounts in the account selector. Then run Smartify, change the Backend in Settings, and update Zelcore. The KDA is safe as long as it is on the blockchain.

Related:

What happened to Kadena in October 2025, and do I need to do anything in Zelcore?​

Answer:

Kadena LLC ended its business operations on 21 October 2025. The blockchain kept running, and on 8 November 2025 it moved to Kadena Community Edition, a community-run continuation. Your addresses, keys and balances did not change, and you do not need to migrate. Keep Zelcore updated. Exchange support for KDA has shrunk, so check your exchange before you deposit.

Related:

I sent KDA to an exchange but they say they didn't receive it. What do I do?​

Answer:

Send the exchange's support the transaction hash, the amount, the chain you used and the deposit account. A deposit on a chain the exchange does not read is not lost on the blockchain, but only the exchange can credit it.

Related:

Monero (XMR) Questions​

For the steps to receive, send and rescan XMR in Zelcore 8.39, see Monero (XMR) in Zelcore.

I'm getting "not enough spendable" error when trying to send Monero, but I have a balance. Why?​

Answer:

The "not enough spendable" error with Monero (XMR) occurs when your displayed balance includes funds that aren't yet available to spend. This is unique to Monero's privacy features and confirmation requirements.

Why this happens:

Monero requires funds to have 10 confirmations before they become "spendable." This is a network-level requirement for privacy and security, not a Zelcore limitation.

Understanding Monero balance states:

Your Monero wallet actually has multiple balance categories:

  • Total balance: All XMR in your wallet (including locked)
  • Unlocked balance: XMR with 10+ confirmations (spendable)
  • Locked balance: Recent XMR with fewer than 10 confirmations (not yet spendable)

Common scenarios:

Scenario 1: Recent deposit

  • You received XMR 5 minutes ago
  • Balance shows correctly
  • But funds need 10 confirmations (~20 minutes)
  • Must wait before sending

Scenario 2: Previous send not fully confirmed

  • You sent XMR recently
  • Change returned to your wallet
  • Change needs 10 confirmations
  • Can't use change yet for new transaction

Scenario 3: Multiple small deposits

  • Received several small XMR payments
  • Some confirmed, some not yet
  • Only confirmed portion is spendable
  • Rest shows as locked

Solutions:

1. Wait for confirmations (most common solution)

Simply wait for your XMR to unlock:

  • Time needed: ~20 minutes for 10 confirmations
  • Monero block time: ~2 minutes per block
  • Check progress: Use Monero block explorer

How to check confirmations:

  1. Get your transaction hash (TxID)
  2. Visit xmrchain.net or localmonero.co/blocks
  3. Search for your transaction
  4. Check confirmation count
  5. When it reaches 10, XMR becomes spendable

2. Check your actual spendable balance

In Zelcore:

  1. Go to Monero (XMR)
  2. Look for balance breakdown if available
  3. May show "Locked" vs "Unlocked" amounts
  4. Only unlocked amount is spendable

3. Send smaller amount

If part of your balance is unlocked:

  • Try sending less than your full balance
  • May work if you have some confirmed funds
  • Error message may indicate exact spendable amount

4. Run Smartify

Refresh your wallet sync:

  1. Go to Settings > Smartify
  2. Wait for completion
  3. Check if spendable balance updates
  4. May resolve sync-related display issues

5. Rescan wallet (if persistent)

If balance seems wrong after confirmations:

  1. In Zelcore, look for Monero rescan option
  2. Or export private keys to official Monero wallet
  3. Import there and rescan
  4. Verifies actual spendable balance

Prevention tips:

  1. Wait after receiving:

    • Always wait 20-30 minutes after deposit
    • Ensures full confirmation
    • Avoid "not enough spendable" errors

  2. Space out transactions:

    • Don't send XMR immediately after sending
    • Change needs time to confirm
    • Wait between sends

  3. Plan ahead:

    • If you know you'll need to send XMR soon
    • Receive/consolidate it in advance
    • Give time for confirmations

  4. Check before urgent sends:

    • Verify spendable balance first
    • Don't assume total balance is sendable
    • Test with small amount if unsure

Understanding why Monero works this way:

Monero's 10-confirmation requirement protects privacy:

  • Prevents double-spend attacks
  • Maintains transaction privacy guarantees
  • Standard across all Monero wallets
  • Network-level rule, not wallet-specific

Related:

My Monero transaction failed with "Error 500" or broadcast error. What should I do?​

Answer:

"Error 500" or broadcast errors when sending Monero typically indicate that Zelcore's Monero node couldn't process or broadcast your transaction to the network. This is usually temporary and has several solutions.

Common causes:

  1. Node sync issues: Zelcore's backend Monero node is out of sync
  2. Network congestion: Monero network experiencing high load
  3. Node connectivity: Temporary connection issues to Monero nodes
  4. Outdated wallet sync: Your local wallet not fully synced
  5. Transaction construction failure: Issue building the transaction

Immediate solutions:

Solution 1: Wait and retry (simplest)

  1. Wait 5-10 minutes
  2. Try sending again
  3. Node issues often resolve quickly
  4. Many broadcast errors are temporary

Solution 2: Run Smartify

Refresh wallet connections:

  1. Go to Settings in Zelcore
  2. Click/tap Smartify
  3. Wait for completion (1-3 minutes)
  4. Try sending transaction again
  5. Refreshes connection to Monero nodes

Solution 3: Change backend/proxy

Switch to different Monero node:

  1. Go to Settings > Backend (or Proxy)
  2. Select different server
  3. Save changes
  4. Run Smartify
  5. Attempt transaction again

Different nodes may have better connectivity.

Solution 4: Update Zelcore

Ensure you're on latest version:

  1. Download latest Zelcore from zelcore.io
  2. Install update
  3. Restart application
  4. Run Smartify
  5. Try transaction again

Newer versions have better node management.

Solution 5: Restart Zelcore

Simple but effective:

  1. Completely close Zelcore
  2. Wait 30 seconds
  3. Reopen Zelcore
  4. Run Smartify
  5. Attempt transaction

Clears any stuck processes.

Solution 6: Check Monero network status

Verify it's not network-wide issue:

  1. Visit Monero community channels (Reddit, Discord)
  2. Check if others reporting issues
  3. Visit Monero block explorers (xmrchain.net)
  4. See if network is processing blocks normally

If network-wide, must wait for resolution.

Solution 7: Use official Monero wallet

If Zelcore consistently fails:

  1. Export your Monero private key from Zelcore
  2. Import into official Monero GUI or CLI wallet
  3. Let it sync (may take time)
  4. Send transaction from official wallet
  5. Monero's own wallet has direct node access

Advanced solution: Rescan wallet

If error persists and seems balance-related:

  1. Look for Monero rescan option in Zelcore
  2. Or use official wallet with rescan
  3. Rebuilds wallet state from blockchain
  4. May take 30-60 minutes
  5. Fixes sync-related broadcast issues

Understanding Error 500:

"Error 500" is a generic server error meaning:

  • Backend node couldn't process your request
  • Could be node-side issue
  • Could be transaction construction problem
  • Not necessarily a problem with your funds
  • Usually temporary

Prevention:

  1. Keep Zelcore updated:

    • Latest versions have better node handling
    • Improved error recovery
    • Better Monero integration

  2. Run Smartify regularly:

    • Weekly preventive maintenance
    • Keeps wallet synced
    • Prevents sync-related errors

  3. Check before urgent sends:

    • Test with small amount first if critical
    • Verify wallet is synced
    • Ensure enough confirmations on balance

  4. Have backup plan:

    • Keep official Monero wallet installed
    • Know your seed phrase/private key
    • Can always use alternative wallet

When to worry:

Don't worry if:

  • Error happens once or twice
  • Resolves after Smartify or wait
  • Other transactions work
  • No other symptoms

Do investigate if:

  • Error persists for hours
  • Happens on every transaction attempt
  • Balance seems incorrect
  • Other Zelcore functions also failing

Important: Broadcast errors don't mean you lost funds. Your XMR is safe on the blockchain. The error just means the transaction couldn't be sent to network.

Related:

My incoming Monero transaction isn't showing in Zelcore, but the sender says it's confirmed. What should I do?​

Answer:

If someone sent you Monero (XMR) and you can verify the transaction on blockchain explorers but it's not showing in Zelcore, this is a wallet sync issue that can usually be fixed.

First: Verify the transaction exists

Before troubleshooting, confirm the transaction is real:

  1. Get transaction details from sender:

    • Transaction hash (TxID)
    • Amount sent
    • Your receiving address they used

  2. Check on Monero explorer:

    • Visit xmrchain.net or localmonero.co/blocks
    • Search for the transaction hash
    • Verify it shows as confirmed
    • Note the block height it was included in

  3. Verify correct address:

    • Confirm sender used YOUR Monero address from Zelcore
    • XMR addresses are long (start with 4 or 8)
    • Even one wrong character = wrong address

If transaction is confirmed on blockchain:

Solution 1: Run Smartify (try this first)

  1. Open Zelcore
  2. Go to Settings
  3. Click/tap Smartify
  4. Wait for completion (1-3 minutes)
  5. Check Monero balance

This fixes most sync issues.

Solution 2: Change backend server

  1. Go to Settings > Backend (or Proxy)
  2. Switch to different server
  3. Save changes
  4. Run Smartify again
  5. Check balance

Different backend may sync better.

Solution 3: Update Zelcore

  1. Download latest version from zelcore.io
  2. Install update
  3. Restart Zelcore
  4. Run Smartify
  5. Check for transaction

Newer versions have improved Monero support.

Solution 4: Rescan Monero wallet

Monero wallets sometimes need rescanning:

In Zelcore (if available):

  1. Look for Monero-specific settings
  2. Find "Rescan" or "Restore height" option
  3. Set restore height to block before transaction
  4. Initiate rescan
  5. Wait for completion (10-30 minutes)

Using official Monero wallet:

  1. Export your Monero private key from Zelcore
  2. Import into Monero GUI or CLI wallet
  3. Set restore height to block before transaction (check on explorer)
  4. Let wallet rescan blockchain
  5. XMR should appear
  6. Can use Monero wallet or wait for Zelcore to sync

Solution 5: Clear cache and restart

  1. Clear Zelcore cache (varies by platform)
  2. Restart Zelcore
  3. Run Smartify
  4. Allow time to resync

Solution 6: Check restore height

Monero wallets use a "restore height" - the blockchain height from which they start scanning:

  1. If transaction occurred before your restore height
  2. Wallet won't see it
  3. Need to set lower restore height
  4. Usually requires rescan

Why this happens:

Monero's privacy creates sync challenges:

  • Transactions are encrypted on blockchain
  • Wallet must scan every block to find YOUR transactions
  • If wallet state is wrong, can miss transactions
  • Requires your private view key to decrypt

Common causes of missing incoming XMR:

  • Wallet restore height set too high
  • Backend node out of sync
  • Local wallet cache corrupted
  • Zelcore didn't scan the specific block
  • Node connectivity issues during that timeframe

Prevention:

  1. Run Smartify regularly:

    • Weekly recommended
    • Keeps wallet synced
    • Catches transactions promptly

  2. Keep Zelcore updated:

    • Better Monero node support
    • Improved scanning
    • Bug fixes

  3. Verify receiving address before giving it out:

    • Screenshot your XMR address
    • Provide correct address to sender
    • One character wrong = different wallet

  4. Have official Monero wallet as backup:

    • Can always verify with official wallet
    • Import same keys
    • Ultimate fallback

Understanding the delay:

Unlike most cryptocurrencies where balance updates are instantaneous (just need confirmations), Monero requires your wallet to:

  1. Scan the blockchain
  2. Decrypt transactions using your view key
  3. Identify which transactions are yours
  4. Update balance

This makes Monero more private but requires proper sync.

Your XMR is safe:

Important to understand: If the transaction is confirmed on blockchain explorers and was sent to your correct address, your XMR is safe. It's not lost, just not displayed in Zelcore yet. Rescanning or using official Monero wallet will reveal it.

When to contact support:

Contact Zelcore support if:

  • Tried all solutions above
  • Transaction confirmed 24+ hours ago
  • Rescan doesn't help
  • Other Monero functions also broken
  • Need help exporting to official wallet

Related:

What is Monero "rescan" and when do I need to do it?​

Answer:

A Monero "rescan" forces your wallet to re-examine the blockchain from a specific point to find all transactions belonging to you. Due to Monero's privacy features, this is sometimes necessary to ensure your wallet displays the correct balance and transaction history.

Why Monero needs rescanning:

Unlike transparent blockchains (Bitcoin, Ethereum) where any wallet can see all transactions, Monero transactions are private:

  • All transactions are encrypted on the blockchain
  • Your wallet must decrypt each transaction using your private view key
  • Wallet "scans" blockchain to find which transactions are yours
  • If scan is incomplete or corrupted, you'll miss transactions

When you need to rescan:

1. After importing/recovering wallet:

  • Imported Monero wallet from seed or keys
  • Need to scan entire blockchain history
  • Finds all your historical transactions

2. Missing incoming transactions:

  • Someone sent you XMR (confirmed on explorer)
  • Not showing in your wallet
  • Rescan will find it

3. Balance shows zero but shouldn't:

  • You know you have XMR
  • Wallet shows nothing
  • Rescan rebuilds balance

4. After Monero protocol upgrades:

  • Major Monero network updates
  • Wallet may need to rescan with new rules
  • Ensures compatibility

5. Wallet sync issues:

  • Inconsistent balance
  • Missing transaction history
  • Strange behavior

How to rescan in Zelcore:

Method 1: If Zelcore has rescan option

  1. Open Zelcore
  2. Go to Monero (XMR) settings
  3. Look for "Rescan" or "Restore from height" option
  4. Enter restore height (block number to scan from)
    • Use 0 for full history (slow)
    • Use block number before first transaction (faster)
  5. Initiate rescan
  6. Wait for completion (10 minutes to several hours)

Method 2: Using Smartify (light rescan)

  1. Go to Settings
  2. Run Smartify
  3. This does a light refresh
  4. May fix minor sync issues
  5. Faster than full rescan

Method 3: Update and rescan

  1. Update Zelcore to latest version
  2. Latest version may have better Monero backend
  3. Run Smartify after updating
  4. May automatically rescan

How to rescan using official Monero wallet:

If Zelcore rescan doesn't work or isn't available:

Step 1: Export your keys from Zelcore

  1. In Zelcore, find Monero private key export option
  2. Safely note your:
    • Mnemonic seed (25 words), OR
    • Private spend key and private view key
  3. Also note your receiving address (verify it's correct)

Step 2: Download Monero GUI Wallet

  1. Visit getmonero.org
  2. Download official Monero GUI for your OS
  3. Verify download authenticity (important for security)
  4. Install wallet

Step 3: Restore wallet in Monero GUI

  1. Open Monero GUI
  2. Select "Restore wallet from keys or mnemonic seed"
  3. Enter your seed or keys
  4. Set restore height:
    • Use block number from before your first transaction
    • Check explorer for block height
    • Or use 0 for complete scan (very slow)
  5. Create wallet password
  6. Begin restore

Step 4: Wait for sync

  1. Monero GUI will download blockchain
  2. Then scan for your transactions
  3. Full sync can take hours or days (depending on restore height)
  4. Progress bar shows status

Step 5: Verify balance

  1. Once sync complete, check balance
  2. Should show all your XMR
  3. Transaction history should be complete
  4. Can send from Monero GUI if needed

Step 6: Return to Zelcore

  1. Your keys are same in both wallets
  2. Can continue using Zelcore
  3. Monero GUI remains as backup
  4. Both wallets access same XMR

Understanding restore height:

Restore height = blockchain block number to start scanning from

Examples:

  • Restore height 0: Scan entire blockchain (complete history)
  • Restore height 2500000: Scan from block 2,500,000 onward
  • Restore height = recent block: Only scan recent activity

How to determine restore height:

  1. Check when you first received XMR (date)
  2. Look up Monero block height for that date
  3. Use block slightly before (e.g., 1 week earlier)
  4. Wallet scans from that point forward

Find block height for date:

  • Visit moneroblocks.info or xmrchain.net
  • Look at historical blocks
  • Match date to block height

Rescan time estimates:

Full scan (restore height 0):

  • Scans entire Monero blockchain
  • 1-7 days depending on hardware
  • Use only if necessary

Partial scan (recent restore height):

  • Scans from specific point
  • Minutes to hours
  • Faster and usually sufficient

In Zelcore Smartify:

  • Light refresh
  • 1-3 minutes
  • May not catch deep issues

Important notes:

1. Your XMR is always safe:

  • Rescan doesn't change blockchain
  • Just updates wallet's view of your balance
  • Keys control XMR, not wallet display

2. Patience is required:

  • Monero scanning can be slow
  • Privacy features require thorough checking
  • Don't interrupt rescan process

3. Keep keys safe:

  • If exporting to Monero GUI
  • Never share keys with anyone
  • Store backup securely
  • Anyone with keys controls your XMR

4. Both wallets work:

  • Can use Zelcore and Monero GUI with same keys
  • They access same funds
  • Useful to have both options

Prevention:

  1. Run Smartify regularly:

    • Keeps Zelcore synced
    • Reduces need for deep rescans

  2. Update Zelcore:

    • Better Monero support over time
    • Fewer sync issues

  3. Note restore height when creating wallet:

    • If you created wallet at block X
    • Never need to scan before X
    • Saves time on future rescans

Related:

How do I export my Monero private keys from Zelcore to use in another wallet?​

Answer:

Exporting your Monero private keys from Zelcore allows you to access your XMR in the official Monero wallet or other Monero-compatible wallets. This is useful for rescanning, verifying balance, or using advanced features.

Important security warnings:

Before exporting keys:

  • Your private keys give COMPLETE control over your Monero
  • Anyone with your keys can steal all your XMR
  • Never share keys with anyone
  • Don't enter keys into unknown websites or apps
  • Only use official Monero wallet or trusted wallets
  • Consider your environment (no cameras, screen recording, etc.)

How to export in Zelcore:

Step 1: Access Monero wallet

  1. Open Zelcore
  2. Go to your Monero (XMR) wallet
  3. Find settings or key export option (location varies by version)

Step 2: Locate private key options

Look for options like:

  • "Export private key"
  • "Show seed phrase"
  • "Backup wallet"
  • "View mnemonic"

Step 3: Export keys

Zelcore should provide one or both:

Option A: Mnemonic seed (25 words)

  • 25-word recovery phrase
  • Easiest for importing to Monero GUI
  • Write down ALL 25 words in exact order
  • Include the 25th word (checksum)

Option B: Hexadecimal keys

  • Private spend key (long hexadecimal string)
  • Private view key (long hexadecimal string)
  • Public address
  • Note all three

Step 4: Safely store

  1. Write keys on paper (most secure)
  2. Or save in encrypted file
  3. Store in secure location
  4. Never in cloud or email unless encrypted
  5. Create multiple backups

What to export:

For Monero GUI import, you need:

Minimum (one of these):

  • 25-word mnemonic seed, OR
  • Private spend key + private view key

Helpful additional info:

  • Wallet address (to verify)
  • Restore height (block number when wallet created)

Using exported keys in Monero GUI:

Step 1: Download Monero GUI

  1. Visit getmonero.org
  2. Download official wallet for your OS
  3. Verify download (check hashes)
  4. Install wallet

Step 2: Restore wallet

If you have 25-word seed:

  1. Open Monero GUI
  2. Select "Restore wallet from mnemonic seed"
  3. Enter your 25 words in order
  4. Set wallet password
  5. Enter restore height (or 0 for full scan)
  6. Click "Create wallet"

If you have private keys:

  1. Open Monero GUI
  2. Select "Restore wallet from keys"
  3. Enter:
    • Account address
    • Private spend key
    • Private view key
  4. Set wallet password
  5. Enter restore height
  6. Click "Create wallet"

Step 3: Sync blockchain

  1. Monero GUI will sync
  2. Downloads blockchain data
  3. Scans for your transactions
  4. Wait for completion (hours to days)

Step 4: Access your XMR

  1. Once synced, balance appears
  2. Can send/receive normally
  3. Advanced features available
  4. Full control over XMR

Common issues when exporting:

Issue 1: Can't find export option in Zelcore

  • Check Zelcore documentation for your version
  • Try Settings > Security > Private keys
  • Update to latest Zelcore version
  • Contact Zelcore support for guidance

Issue 2: Only seeing public address

  • Public address alone isn't enough
  • Need private keys or seed
  • Look for "Show private key" option
  • May require additional authentication

Issue 3: 24 words instead of 25

  • Monero uses 25-word seeds (not 24)
  • Ensure you have all 25 words
  • 25th word is checksum/verification
  • If only 24, may be wrong export or different wallet type

After exporting, you can:

  1. Import to Monero GUI:

    • Access same XMR from official wallet
    • Better for troubleshooting
    • More advanced features

  2. Verify balance independently:

    • Check if Zelcore showing correct balance
    • Monero GUI shows definitive balance

  3. Perform deep rescan:

    • Monero GUI rescans entire blockchain
    • Finds all transactions
    • Fixes sync issues

  4. Send XMR if Zelcore has issues:

    • If Zelcore broadcast failing
    • Use Monero GUI to send
    • Direct node connection

Important: Same keys = same wallet

Understanding the concept:

  • Zelcore and Monero GUI with same keys access SAME XMR
  • Not two separate wallets
  • Just different interfaces to same blockchain account
  • Sending from one affects the other
  • Both see same transactions

Security best practices:

  1. Physical security:

    • Write seed on paper, not digital
    • Store in fireproof safe
    • Consider metal backup for fire protection
    • Multiple secure locations

  2. Digital security:

    • If saving digitally, encrypt the file
    • Use strong encryption (VeraCrypt, etc.)
    • Never plain text
    • Definitely not in email or cloud

  3. Verification:

    • After writing seed, verify accuracy
    • Double-check each word
    • Test recovery with small amount first

  4. Environment:

    • No cameras around when viewing keys
    • No screen sharing software
    • Trusted device only
    • Secure internet connection

When to export keys:

Good reasons:

  • Need to rescan with Monero GUI
  • Want backup in official wallet
  • Zelcore has persistent issues
  • Want to verify balance independently
  • Preparing for device change

Not necessary:

  • Normal Zelcore usage works fine
  • Just to check balance (use explorer)
  • Someone asks for keys (NEVER share)

Remember: Your keys, your Monero. Protect them like the valuable asset they represent.

Related:

Solana (SOL) Questions​

My Solana transactions are failing with "blockhash not found" or similar errors. What's wrong?​

Answer:

Solana transaction failures, especially after network upgrades or during periods of network congestion, are often caused by the blockchain's unique architecture and Zelcore's interaction with Solana RPC nodes.

Common error messages:

  • "Blockhash not found"
  • "Transaction simulation failed"
  • "Block height exceeded"
  • "Unable to confirm transaction"
  • "Network request failed"
  • "Transaction expired"

Why Solana transactions fail:

1. Solana's blockhash expiration:

  • Solana transactions require a recent blockhash
  • Blockhashes expire very quickly (approximately 60-90 seconds)
  • If transaction isn't confirmed before expiration, it fails
  • Much faster expiration than Bitcoin or Ethereum

2. Network congestion:

  • High network activity causes delays
  • Transactions may not be processed before blockhash expires
  • Priority fees become more important during congestion
  • Network upgrades can temporarily increase failures

3. RPC node issues:

  • Zelcore connects to Solana through RPC nodes
  • Node may be out of sync or overloaded
  • Node might not have latest blockhash
  • Connection issues between Zelcore and node

4. After network upgrades:

  • Solana has frequent network upgrades
  • New consensus rules or protocol changes
  • RPC nodes need time to update
  • Temporary incompatibilities during transition

Immediate solutions:

Solution 1: Wait and retry (simplest)

  1. Wait 2-3 minutes after failed transaction
  2. Solana network often self-corrects quickly
  3. Retry the transaction
  4. If fails again, proceed to other solutions

Solution 2: Run Smartify

Refresh Zelcore's connection to Solana network:

  1. Go to Settings in Zelcore
  2. Click/tap Smartify
  3. Wait for completion (1-3 minutes)
  4. Try transaction again
  5. Forces reconnection to RPC nodes with fresh state

Solution 3: Update Zelcore

  1. Check if newer Zelcore version is available
  2. Download from zelcore.io
  3. Install update
  4. Restart Zelcore
  5. Run Smartify
  6. Retry transaction

Network upgrades often require wallet updates for compatibility.

Solution 4: Change backend/proxy server

Switch to different Solana RPC endpoint:

  1. Go to Settings > Backend (or Proxy)
  2. Select different server
  3. Save changes
  4. Run Smartify
  5. Attempt transaction again

Different RPC nodes may have better sync or lower load.

Solution 5: Reduce transaction complexity

If sending to multiple recipients or complex transaction:

  1. Break into smaller, simpler transactions
  2. Send one at a time
  3. Wait for each to confirm before next
  4. Simpler transactions have higher success rate

Solution 6: Increase priority fee (if available)

During network congestion:

  1. Look for priority fee or network fee setting
  2. Increase slightly above default
  3. Higher priority = faster processing
  4. Helps avoid blockhash expiration

Note: Zelcore may not expose priority fee controls. If not available, timing and retry is your best strategy.

Solution 7: Use Phantom or Solflare wallet temporarily

If Zelcore consistently fails:

  1. Export your Solana private key from Zelcore
  2. Import into Phantom or Solflare wallet
  3. Send transaction from native Solana wallet
  4. They often have better Solana RPC connectivity
  5. Return to Zelcore after urgent transaction

How to export Solana key from Zelcore:

  1. Go to Solana in Zelcore
  2. Find private key export option
  3. Safely note your private key or seed phrase
  4. Import into Phantom/Solflare using their import function

Understanding Solana network upgrades:

Solana upgrades frequently:

  • Scheduled network upgrades every few months
  • Improve performance and add features
  • Can temporarily affect transaction success rates
  • Usually resolved within 24-48 hours

What happens during upgrades:

  • Validators update to new version
  • Brief period of higher failure rates
  • RPC nodes may lag behind
  • Wallets need compatibility updates

How to know if it's an upgrade issue:

  1. Check Solana status:

    • Visit status.solana.com
    • Check Solana Twitter (@solana)
    • Look for upgrade announcements
    • Community channels (Discord, Reddit)

  2. Check if widespread:

    • Search "Solana transaction issues" on Twitter
    • Check Solana subreddit
    • If many users reporting, likely network-wide
    • If just you, likely Zelcore/RPC specific

  3. Timeline:

    • Network-wide issues resolve in hours to 1-2 days
    • Zelcore-specific issues need wallet update or workaround

Prevention tips:

1. Time your transactions:

  • Avoid sending during peak congestion
  • Check Solana network activity first
  • If urgent, increase priority fee
  • Patience during network upgrades

2. Keep Zelcore updated:

  • Updates include Solana compatibility improvements
  • Better RPC node handling
  • Bug fixes for transaction construction
  • Check for updates monthly

3. Run Smartify regularly:

  • Weekly maintenance recommended
  • Keeps RPC connections fresh
  • Prevents stale blockhash issues
  • Quick preventive measure

4. Monitor Solana network:

  • Follow @solana on Twitter
  • Join Solana Discord
  • Aware of planned upgrades
  • Expect temporary issues during upgrades

5. Have backup wallet:

  • Keep Phantom or Solflare installed
  • Import same keys
  • Use if Zelcore has issues
  • Multiple access points to your SOL

When to worry vs. when to wait:

Don't worry if:

  • Error happens once or twice
  • Resolves with retry
  • Solana network upgrade just happened
  • Other Zelcore functions working fine

Do investigate if:

  • Fails repeatedly over hours
  • Balance shows incorrectly
  • Other Solana wallets also failing
  • Errors persist days after network upgrade

Specific error troubleshooting:

"Blockhash not found":

  • RPC node doesn't have that blockhash anymore
  • Transaction took too long to process
  • Run Smartify and retry immediately
  • If persistent, change backend server

"Transaction simulation failed":

  • Transaction would fail if executed
  • Check you have enough SOL for fee
  • Verify recipient address is correct
  • May indicate insufficient balance or invalid operation

"Block height exceeded":

  • Transaction expired (blockhash too old)
  • Retry transaction to get fresh blockhash
  • If keeps happening, RPC node is slow

"Unable to confirm transaction":

  • Transaction may have been sent but confirmation uncertain
  • Check Solana explorer (solscan.io or explorer.solana.com)
  • Search your address to see if transaction appeared
  • If confirmed on chain, just display issue in Zelcore

Checking transaction status on blockchain:

  1. Get your Solana address from Zelcore
  2. Visit solscan.io
  3. Search your address
  4. Check recent transactions
  5. See if failed transaction appears
  6. Confirms whether it's send issue vs. display issue

Advanced: Understanding Solana's transaction lifecycle

Why Solana is different:

Unlike Bitcoin/Ethereum:

  • Extremely fast finality (400ms)
  • But also fast expiration of transaction validity
  • Trade-off: speed vs. longer validity window
  • Requires more real-time connectivity

Transaction steps:

  1. Wallet gets recent blockhash from RPC node
  2. Transaction constructed with blockhash
  3. Transaction signed
  4. Broadcast to network
  5. Must be confirmed within ~60-90 seconds
  6. Otherwise blockhash expires and transaction invalid

Where it can fail:

  • Step 1: RPC node slow or out of sync
  • Step 4: Network congestion delays broadcast
  • Step 5: Not processed before expiration
  • Between steps: Any delay can cause failure

When network is healthy:

  • Transactions confirm in 1-2 seconds
  • Rarely fail
  • Smooth experience

When network is stressed:

  • Delays at any step
  • Higher failure rates
  • Multiple retries needed
  • Frustrating user experience

Important notes:

Your SOL is safe:

  • Failed transactions don't lose funds
  • SOL remains in wallet if transaction fails
  • Can retry as many times as needed
  • No penalty for failed attempts

Small fee may be charged:

  • Even failed transactions may consume tiny fee
  • Usually 0.000005 SOL (negligible)
  • For network processing
  • Don't worry about losing significant SOL to fees

Zelcore vs. Solana:

  • Most issues are Solana network behavior
  • Not Zelcore bugs
  • All wallets experience similar issues during congestion
  • Native Solana wallets may handle slightly better

Related:

Horizen (ZEN) Questions​

Why can't I send ZEN from my Horizen wallet in Zelcore?​

Answer:

Horizen's mainchain stopped at block 1,807,300 when ZEN moved to Base. Because that chain no longer produces blocks, Send is disabled for mainchain ZEN in Zelcore 8.39.0 and later.

What you can still do:

  • Your mainchain ZEN balance and history stay visible in Zelcore
  • ZEN on Base is available in Zelcore as Horizen BASE Token

Why was my ZEN balance or history empty for a while?

The old ZEN explorers now show the Base network, so Zelcore could no longer load the mainchain balance and history. In 8.39.0 Zelcore loads them again from Horizen's legacy explorer.

note

The Horizen mainchain may be removed from Zelcore in a future version. Click the notification in the app to read more.

Kaspa (KAS) Questions​

Why are my KRC-20 token transfers paused?​

Answer:

Zelcore pauses KRC-20 transfers while the Kasplex indexer is unavailable. Kasplex asked all wallets to do this, and transfers resume when the indexer is back.

What this means for you:

  • Your tokens are safe. Try the transfer again later.
  • While the indexer is down, Zelcore shows the last known token balance with its date, or says the balance cannot be loaded until the indexer returns.
  • Token history cannot be loaded either during that time.
  • Your KAS is not affected. Sending KAS continues to work.

KRC-20 balances and history come from the Kasplex indexer, and Zelcore is not responsible for the accuracy of indexer data.

Related:

Polkadot (DOT) and Kusama (KSM) Questions​

Why did Polkadot or Kusama show "Error while obtaining Polkadot transactions"?​

Answer:

Before Zelcore 8.39.0, Polkadot and Kusama transaction history could fail to load with the error "Error while obtaining Polkadot transactions". This is fixed in 8.39.0, and the history loads again. Update Zelcore to the latest version if you still see the error.

Related: