Transaction confirmed, but crypto still not received?
Confirmed only means the blockchain accepted the transaction. It does not mean an exchange has credited your account. Those are two separate systems, and the gap is where most missing deposits live.
Paste the TXID to see the confirmation count, destination and network before you open a ticket. A green explorer tick is not a support answer on its own.
What usually causes this
These are the common explanations for this category of problem. Which one applies to your transfer depends on your transaction, the network it used and the destination's deposit rules — that is what the check above works out.
- The platform's confirmation requirement is higher than the confirmations you have
- The deposit can't be matched to your account because a tag or memo is missing
- The asset arrived on a network the platform doesn't credit
- The platform has credited it internally but hasn't updated your visible balance yet
Confirmations required, platform by platform
The same transfer is 'not yet confirmed enough' at one platform and long since credited at another, because the threshold is a business decision rather than a property of the network. Comparing them is the quickest way to see whether your wait is normal.
| Platform | Bitcoin | Ethereum | TRON | Polygon | Solana |
|---|---|---|---|---|---|
| Binance | 1 | 6 | 1 | 100 | 32 |
| Coinbase | 3 | 35 | 1 | 200 | 32 |
| Kraken | 4 | 20 | 20 | 120 | 32 |
| Crypto.com | 1 | 12 | 1 | 100 | 32 |
| Bybit | 1 | 6 | 1 | 100 | 32 |
| OKX | 1 | 12 | 1 | 100 | 32 |
| KuCoin | 2 | 12 | 1 | 100 | 32 |
| Revolut | 3 | 30 | 20 | 150 | 32 |
Approximate, reviewed 2026-08. A dash means the platform does not credit deposits on that network, or does not publish a figure.
Where the platform deposit figures come from
- Binance support centre
- Coinbase support centre
- Kraken support centre
- Crypto.com support centre
- Bybit support centre
- OKX support centre
- KuCoin support centre
- Revolut support centre
Policy snapshot 2026-08; verify in-account.
Confirmed on an explorer is not a support answer
Support still needs the hash, the confirmation count and the destination address. Opening a ticket because Etherscan turned green, without those fields, usually comes back as expected behaviour. Generate the evidence pack from the TXID before you write the paragraph.
- Turn a confirmed TXID into a support message — Includes status and confirmation count from the public record.
What you get, and what it costs
Free, always
The transaction check: network, asset, amount, both addresses, timestamp, on-chain status, confirmation count, and a copyable evidence message for support. No diagnosis.
£9.99, one-off
The diagnosis: the likely cause, recovery outlook, step-by-step instructions, the official support route, wording written for that case, and 72-hour monitoring. No subscription.
Questions
How many confirmations does an exchange need?
It varies by exchange and by chain — from one confirmation on some chains to over a hundred on others. TXLens compares your transaction against the destination's typical requirement as part of the diagnosis.
Should I contact support straight away?
Not if you are still inside the normal confirmation window: the ticket will be closed as expected behaviour. TXLens tells you whether you are still waiting or whether something is genuinely wrong.
Related
Platform requirements on this page were last reviewed 2026-08. They change without notice, which is why every diagnosis is phrased as a likely cause rather than a certainty.
TXLens is read-only. We only use your transaction ID and public blockchain data. We never ask for your private keys, seed phrase or exchange login.