A crypto exchange requires confirmations because an onchain transaction can appear before its place in the ledger is sufficiently difficult to reverse. The exchange waits for a network specific threshold before turning the incoming transfer into a spendable internal balance. On many networks, one confirmation means inclusion in a block. It does not mean universal or immediate irreversibility.

What does one confirmation mean?

A wallet can display a transaction as soon as it is broadcast. At that stage, the transaction may be visible to network nodes and an explorer but still be waiting for inclusion in a block. On many blockchains, the first confirmation arrives when a validator or miner includes the transaction in a block.

For proof of work networks, every later block normally adds depth above that transaction. Replacing the transaction becomes progressively harder as more blocks build on top of it. Proof of stake networks can use checkpoints and explicit finality states instead. This is why a raw confirmation count is not directly comparable across every blockchain.

Status What it usually tells you What it does not guarantee
Seen by a wallet or explorer The transaction has been broadcast and detected Inclusion in a block
Included in a block The transaction has its first confirmation on many networks That every exchange will credit it immediately
Venue threshold met The exchange has observed its required network depth or finality state That internal account processing is complete
Credited The venue has added the deposit to the customer account That withdrawal or product eligibility is available in every country

Why does an exchange wait?

An exchange credits an onchain transfer to an offchain account system. If it made the balance spendable too early and the blockchain later reorganized, the deposit could disappear from the accepted chain after the customer had already traded or withdrawn against it. Waiting reduces that settlement risk.

The waiting rule also gives the venue time to confirm that the transfer used a supported asset, network and deposit format. A valid blockchain transaction and a credited exchange deposit are separate events. The network confirms the transaction. The exchange then applies its own security and account controls.

Why do required counts differ?

There is no universal safe number. A venue can change its threshold according to the network consensus model, block timing, observed security, asset support, deposit value and current network conditions. The same asset sent on two different networks can therefore have different requirements.

A venue may also pause or delay deposits during maintenance, a network upgrade or a security review. Its product availability and account rules can differ by country. Check the venue status page and the deposit screen for the exact asset and network rather than relying on a number copied from another exchange.

How long could five confirmations take?

Consider a hypothetical network with an assumed average block interval of four minutes. Suppose the first block includes the transfer seven minutes after broadcast and the venue requires five confirmations.

  1. The first included block provides confirmation one after seven minutes.
  2. Four additional blocks are needed to reach confirmation five.
  3. Four blocks multiplied by four minutes equals sixteen minutes.
  4. Seven minutes plus sixteen minutes gives an illustrative total of twenty three minutes.

This is an estimate, not a promise. Block intervals vary and the venue may need extra internal processing time after the network threshold is met. The receiver does not pay an extra network fee merely because it waits for more confirmations.

How can you check a pending crypto deposit?

  1. Confirm the asset and network selected on both the sending wallet and the exchange deposit page.
  2. Open the transaction hash in the correct network explorer.
  3. Check whether the transaction is pending, included or finalized.
  4. Compare its current depth or finality state with the venue requirement shown for that asset and network.
  5. Check any memo, destination tag, minimum deposit and maintenance notice.
  6. If the threshold is met but the balance is missing, contact the venue with the transaction hash and account details. Never send a second transfer automatically.

For a structured safety check before sending, read Wallets, custody and safe transfers. To understand what an explorer can and cannot prove, read Reading blockchain transactions without guessing intent.

What confirmations do not prove

Confirmations show the transaction position or finality state on a particular network. They do not prove the identity or intent of the person behind an address. They also do not repair an unsupported network, an incorrect destination, a missing memo or a transfer below the venue minimum.

Never share a private key or recovery phrase with an exchange support agent. A legitimate transaction hash is public and is normally sufficient for the venue to investigate the onchain leg of a deposit.

Primary sources

Reviewed on 14 November 2026. This article is educational and does not recommend a transaction, venue or asset. Network rules, venue thresholds and eligibility can change.