A crypto transfer shows a confirmation count that rises over time, and platforms require a threshold before crediting funds. The number is a measure of how hard the transaction is to undo.
Inclusion in a block is the first confirmation
A broadcast transaction waits in a pool of pending transactions until a block producer includes it in a block. That inclusion is one confirmation.
At that moment the transaction is recorded, but the block itself is not yet permanent. Another valid block could be produced at the same height by a different participant.
Networks resolve such competition by a rule that selects one chain over the other, and transactions in the discarded block return to pending status.
Each subsequent block deepens the record
When a block is built on top of the one containing a transaction, reversing that transaction would require replacing both blocks rather than one.
Every additional block raises that cost, because the work or stake behind each of them would have to be outcompeted by a competing chain.
The confirmation count is therefore a depth measure, and the probability of reversal falls sharply as it rises rather than reaching a defined zero.
Thresholds differ by network and by amount
Networks produce blocks at different intervals and use different consensus rules, so a given count means different things across chains.
Platforms set their own thresholds based on the network and often on the size of the transfer, which is why a large deposit can be credited more slowly than a small one.
Some newer networks provide a defined finality point after which reversal is not possible under the protocol's rules, changing the question from probability to a stated guarantee.
Waiting for the pool is a separate delay
A transaction with a fee below what block producers are currently accepting may sit pending for a long time without reaching even one confirmation.
That is a congestion problem rather than a confirmation problem, and it resolves when fees fall or when the sender replaces the transaction with a higher-fee version where supported.
Distinguishing the two states matters, because a pending transaction has not happened at all while an unconfirmed one has happened and is not yet deep.
Why exchanges add their own delay
Beyond network confirmations, platforms apply internal review before crediting or releasing funds, covering compliance checks and fraud screening.
That review is invisible on the blockchain, which is why an explorer can show a transaction fully confirmed while the receiving account still shows nothing.
The two systems answer different questions: the network confirms that the ledger changed, the platform decides when it will act on that change.