Confirmed on the blockchain is not credited by the exchange
Confirmed means a block containing the transfer has been accepted by the network. Credited means a company's internal ledger increased a customer's balance. Those events are operated by different computers with different rules.
The gap is where most 'it is confirmed but not received' searches live. It is usually not theft and it is usually not a broken chain.
What an explorer is allowed to claim
An explorer reads the chain. It can say the transfer succeeded, how many blocks have been built on top of it, which token contract moved, and which address received it. It cannot see Binance's deposit watcher, Coinbase's review queue, or Kraken's destination-tag matcher.
When an explorer says success and an exchange says nothing, believe both. They are answering different questions.
- Kraken: deposit confirmations and processing times — Official exchange explanation that credit waits for a confirmation threshold, not for the first explorer tick.
Thresholds that make 'confirmed' premature
In the snapshot TXLens reviews, Coinbase waits for 35 Ethereum confirmations and Kraken waits for 20. Binance waits for 6 on Ethereum and 120 on Arbitrum. TRON USDT is often one confirmation at Binance and 20 at Kraken. The same hash can be 'done' for one destination and 'still confirming' for another.
| If the explorer shows | And the destination is | Usual reading |
|---|---|---|
| Success, 1–2 confirmations | Coinbase ERC20 USDT | Still inside a normal Ethereum wait |
| Success, 1 confirmation | Binance TRC20 USDT | Chain is done; remaining delay is Binance's credit job |
| Success, 20 TRON confirmations | Kraken TRC20 USDT | Threshold in this snapshot; then Kraken's credit delay |
| Failed / reverted | Any exchange | Nothing arrived; do not open a missing-deposit ticket |
Confirmation figures are TXLens's reading of published rules, reviewed 2026-08. The in-account deposit screen wins.
When waiting stops being the answer
Those are the cases a diagnosis is for. Inside the confirmation window, a paid report cannot make the chain go faster.
- The hash is past the destination's documented threshold and an hour or more has gone by.
- The token or network is not on the destination's deposit list.
- A memo or destination tag was required and is absent on-chain.
- The amount is below the published minimum.
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
The explorer says confirmed. Can the exchange still reverse it?
Exchanges wait for a depth of confirmations specifically to make a chain reorganisation expensive. After their threshold, they treat the credit as theirs to keep. Before the threshold, they have credited nothing, so there is nothing to reverse.
Should I contact support as soon as the explorer turns green?
Not if you are still inside that platform's confirmation requirement for the chain. The ticket will be closed as expected behaviour. Compare the confirmation count with the destination's figure first.
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.