Why your wallet shows a zero balance during verification

You submitted your wallet address and it shows a balance of zero — even though you know the funds are there. This is common and almost never means anything is wrong. Here's what's actually happening.

A public address is not your whole wallet

Modern wallets are hierarchical deterministic (HD): a single recovery phrase derives thousands of individual addresses. Your wallet app shows the combined balance across all of them, but a block explorer — or any tool checking a single address — only sees the one address you pasted. The funds are very likely sitting on other addresses derived from the same seed.

Bitcoin and the "change address" trap

In Bitcoin's UTXO model, when you spend from an address the leftover "change" is sent to a brand-new change address, not back to the original. So an address that clearly received coins in the past can correctly show zero today — the balance simply moved to a change address your wallet controls but you never see.

Stealth and one-time addresses

Some assets and privacy protocols (Monero by default, among others) generate a fresh one-time address for every incoming payment. The public address you share never directly holds a visible balance on a normal explorer — by design.

Fresh or receive-only addresses

If you copied a newly generated receiving address that hasn't been funded directly, it reads zero even though your wallet holds plenty elsewhere.

What to do

A zero reading doesn't block you. The most reliable path is test-transfer (dust) verification: you send a tiny amount from your funded wallet. That cryptographically proves you control the funds and lets the verifier observe and link the address actually holding your balance — including HD-derived or change addresses a single-address lookup would miss. Alternatively, provide the specific address that currently holds the balance.