A zero on the screen is a starting point
After restoring a crypto wallet, an empty balance can mean that you opened a different account, selected another network, omitted a passphrase, or have a display or discovery problem. It can also reflect real transactions. Work out which evidence applies before resetting the wallet again or accepting a recovery offer.
This guide covers diagnosis after a conventional self-custody wallet restore. It does not promise recovery or replace the maker's instructions for your model and backup format. An exchange login, a smart-contract wallet's recovery process and a seed-based wallet are different systems.
Start with information that is safe to inspect: the original public account address or transaction record, network, asset, wallet application and account type. Keep recovery words, private keys and passphrases out of websites, support chats and AI prompts. Preserve a working device; do not erase it merely to repeat this exercise.
First check which account you actually restored
For an account-based wallet, compare the full address with a trusted previous record, such as your own withdrawal receipt. A custom name like Savings is only a label. The label may disappear after restoration or be applied to a different account, so it cannot establish identity.
MetaMask's current recovery documentation distinguishes accounts derived from the same Secret Recovery Phrase from separately imported accounts. In an SRP-only restore, accounts imported using a private key or JSON file, and connected hardware wallets using other backups, do not automatically return with that phrase. Its social-login recovery flow differs; first identify which setup you originally used.
An additional account derived from the same phrase may need to be added again through the wallet's documented account sequence. MetaMask gives the example of a later account holding tokens but no mainnet ETH. Check the recovered address rather than assuming the first visible account is the funded one. Follow the current official procedure; do not send secrets to an account-search website.
Bitcoin needs an extra distinction: a wallet can manage many receive and change addresses. The latest receive address need not equal one used last year. Compare the relevant account and transaction history; one newly generated Bitcoin address showing zero does not establish that the whole wallet is empty.
Then match the network and the actual asset
The same-looking account address can be used on multiple EVM networks, while balances and transactions remain specific to each network. Check the network on the original transfer record and in the wallet. Switching the viewing network does not move funds between chains.
MetaMask recommends checking confirmation status, the selected network and the account on that network's block explorer. If the correct token is present there but absent from the app, token detection or display settings may be the issue. Check the contract address before adding a custom token; a matching ticker alone does not identify it.
Keep token units separate from a displayed currency value. An app showing 25 token units but no dollar estimate presents a different question from an account with zero units. An explorer is an independent view to compare, not proof that you control the signing keys or that a token is valuable.
Open the explorer through an independently verified network or wallet reference. Reading a public address or transaction does not require a wallet connection or a signature. Posting that address publicly can associate your identity with its history, so keep your diagnostic record private.
A passphrase is different from a PIN or app password
For wallets using BIP 39, the mnemonic and optional passphrase jointly produce the seed. An omitted passphrase is treated as an empty string. A different passphrase produces a valid seed, so opening a wallet successfully is not proof that you opened the intended funded wallet.
Trezor documents case and spacing differences as possible reasons for opening a different passphrase wallet. The same passphrase combined with another wallet backup also leads elsewhere. Its empty-wallet message describes the balance and history found on enabled networks; a disabled network is another possibility to check.
A device PIN or app-unlock password is not a replacement for the original wallet passphrase. Check your private recovery plan for whether a passphrase was used and which backup it belongs to. Only follow the maker's verified process on the appropriate trusted interface. Do not improvise a new passphrase and expect it to reveal the old account.
Do not change spelling, translate backup words or discard an apparently valid backup because a balance looks wrong. A format check can detect some mistakes, but it cannot certify that the material belongs to your expected account. This lesson deliberately includes no sample recovery phrase to import.
Why a compatible backup may still need account discovery
A derivation path tells a deterministic wallet which branch of its keys to use. BIP 44 describes separate levels for purpose, coin type, account, receive/change branch and address index. This helps explain why two applications need compatible account settings as well as the right backup.
BIP 44's discovery procedure uses transaction history, not just today's balance. It also specifies an external-address gap limit of 20 consecutive unused addresses. That is a rule in this specification, not a universal limit for every wallet or every account type.
Record the original wallet application, network and account type. If moving between compatible applications, consult their official recovery documentation about supported account types and discovery. Do not randomly modify derivation settings on a funded wallet or use an online seed converter to search for a balance.
For Bitcoin, distinguish an old address whose outputs have been spent from the wallet's current unspent outputs. The wallet may hold change at another address. A provider can explain account discovery using non-secret configuration details; it does not need your backup words.
Worked example: three empty screens, three different clues
These are fictional records, not real addresses or transactions. Case A starts with a transfer receipt showing 0.40 ETH to Account Cedar on Network Blue. The restored app is looking at Account Cedar on Network Green and shows zero. The comparison has not yet matched the network. Check Cedar on Blue before concluding that the restore lost anything.
Case B uses the right network, but the app displays Account Maple while the previous receipt identifies Cedar. Adding a token to Maple will not make it Cedar. Establish whether Cedar was another derived account, an imported account or a connected hardware account, then follow that account type's recovery procedure.
Case C is a Bitcoin worksheet. An old receive address now has no unspent output, but the correct wallet account lists two unspent outputs of 23,000 and 17,000 sats. Their total is 40,000 sats, or 0.0004 BTC. The zero at the old address and the nonzero account balance answer different questions.
The arithmetic in Case C assumes those two outputs belong to this wallet and are unspent at the time checked. It does not establish that they can immediately be spent, that the wallet holds no other assets, or that anyone possesses the required keys.
Now change Case A: the correct network shows a confirmed outgoing transaction that the owner does not recognize. That observation deserves an incident investigation, not repeated token-display changes. Preserve the transaction reference and consult the maker's verified incident guidance. Do not label a real person an attacker from an address alone or assume a restore can reverse a completed transfer.
Write a diagnostic record without disclosing secrets
Make one row per observation: expected account, observed account, network, asset or contract, last known transaction, application version, what the explorer shows, and what the wallet shows. Include the time and timezone. Mark uncertain fields as unknown rather than filling them with guesses.
Choose the next check from the mismatch. Different account: investigate the original account type. Different network: compare the correct chain. Same account and network with visible on-chain units: investigate display or synchronization. Unexpected outgoing history: follow the incident process. Keep each observation separate from the explanation you are still testing.
Prompt for a fictional practice exercise: Classify Cases A, B and C into account mismatch, network mismatch or address-versus-wallet balance confusion. State what the evidence establishes, what remains unknown, and the next read-only check. Verify the satoshi conversion. Do not request recovery words, private keys, passphrases, passwords, signatures or real account details.
If you need support, use the provider's independently verified channel and share only the minimum relevant non-secret evidence. A public balance check cannot verify your entire recovery setup. Stop any route that asks you to pay an unlocking fee or surrender signing material to prove ownership.
- The original account type and recovery method are identified.
- Account, network and asset are compared separately.
- A single Bitcoin receive address is not treated as the entire wallet.
- The original passphrase requirement is checked privately.
- Observed transactions are distinguished from display errors and assumptions.
- No working wallet is wiped and no secret is entered into an online checker.
Sources & further reading
- MetaMask: accounts missing after recovery
- MetaMask: missing tokens and incorrect balances
- Trezor: passphrase wallets that appear empty
- BIP 39: mnemonic and passphrase inputs
- BIP 44: account hierarchy and discovery
Educational content. Examples are illustrative. Protocols, products and rules can change; consult the linked documentation for current details.
