To fix wallet balance discrepancies, first check node cache, then derivation path. Over 90% of "incorrect balances" are display delays caused by node cache or network configuration. Derivation path issues typically occur only after restoring a wallet or switching devices.
1. First Step: Check Node Cache
Most balance sync issues are due to the frontend display not being in sync with the actual on-chain state — your assets are not lost.
Step 1: Force Refresh Wallet Data
What to do: Manually trigger the wallet to re-read on-chain data.
How to do it:
Case A (pull-down refresh): On the wallet asset page, pull down from the top to trigger a refresh.
Case B (restart app): Completely exit the wallet app and reopen it. Some caches are cleared upon restart.
Case C (clear cache): Find "Clear Cache" or "Clear Temporary Data" in the wallet settings and execute it.
How to know it's done: The balance changes or shows the latest transaction update.
Step 2: Switch RPC Node
What to do: Change the backend node the wallet connects to, bypassing potential delays or stale data from the current node.
How to do it:
For imToken: Go to "Me - Node Settings" and switch the current network to another public node (e.g., from "Auto" to "Infura").
For TokenPocket: Tap the top-left corner of the wallet asset page and select a low-latency node.
Choose a stable, low-latency node. If the node hasn't updated its data, your asset display will lag.
How to know it's done: The balance returns to normal after switching.
Step 3: Cross-Verify with a Block Explorer
What to do: Bypass the wallet's frontend display and check real on-chain data directly.
How to do it:
Based on the chain you are using, open the corresponding block explorer (Etherscan for Ethereum, BSCScan for BNB Chain, Solscan for Solana).
Paste your wallet address into the search box.
Check the address's balance and transaction history.
How to know it's done: The balance shown on the block explorer matches what you expect. If it does, your asset security is intact — it's only a wallet display issue. If not, the assets may not have actually arrived.
Prerequisite: You hold the wallet's private key or mnemonic phrase. If you restored the wallet from a mnemonic and the balance is abnormal, see the next steps.
2. Second Step: Check Derivation Path
If the block explorer shows the correct balance but the wallet still doesn't display it, and you've just restored the wallet or changed devices, it's highly likely a derivation path mismatch.
Step 4: Confirm Derivation Path Matches
What to do: Check whether the derivation path used when restoring the wallet is the same as the one used when the wallet was created.
How to do it:
Case A (Ethereum / EVM chains): imToken's default path is m/44'/60'/0'/0/0. If you modified the path earlier or created the wallet with another wallet, you'll need to select "Custom Path" during import to match it.
Case B (Bitcoin): Different wallets may use different paths (such as BIP-44, BIP-84). If you connect a Ledger to THORSwap and the balance shows zero, it's likely because it's connected to a different derivation path; adjust the index or change the path.
Case C (Multi-chain wallets): Coinomi supports custom derivation paths when adding tokens. First check the path value on the original wallet, then add the corresponding network wallet with the same path in the new wallet, ensuring the addresses match.
How to know it's done: After re-importing with the correct derivation path, both balance and address display correctly.
Common Causes
"The same wallet shows different balances on different devices" — This is often due to inconsistent derivation paths. Especially when restoring across different wallet brands (e.g., Ledger vs Phantom, TokenPocket vs imToken), their implementation of derivation paths may differ. Another scenario: two nodes haven't synced address generation state — one node generated a new address that received funds, but the other node doesn't know about that address, so it can't scan that transaction.
Risk Reminder: Do not make large transfers before troubleshooting is complete. If the wallet cannot display an asset on a certain chain but the block explorer shows a balance, blindly sending a transaction could overwrite or lose assets at that address. When dealing with multi-chain assets, always confirm the network type of the receiving address.
How to Confirm the Issue Is Resolved After These Steps?
Once your wallet balance matches the block explorer and you can successfully send a small test transaction (I recommend 0.001 SOL or equivalent token to an exchange) and confirm it's credited — only then can you consider the problem solved. If you've tried all the above and the balance still hasn't recovered, consider backing up your mnemonic and re-importing the wallet (always do this in an offline environment), or contact the wallet's official support for verification.
