When you send crypto, your wallet may show the transaction as sent within seconds, but the network has not finished with it yet. A confirmation means a block containing your transaction has been added to the chain, and each block added after it adds another confirmation. Until enough confirmations accumulate, the transaction can theoretically still be reorganised out of the chain, which is why exchanges and merchants wait before crediting your deposit.

The reason is how blockchains reach agreement. Different chains add blocks at different speeds: Bitcoin averages about ten minutes per block, while Ethereum averages around twelve seconds and some chains finalise in under a second. A single confirmation on a fast chain therefore means far less elapsed time than one on Bitcoin, but the principle is the same: each new block buried on top of yours makes it exponentially harder and more expensive for anyone to rewrite history and reverse your transaction.

The risk confirmations guard against is a chain reorganisation, where two competing versions of recent history exist briefly and the network eventually picks one. A transaction in the discarded version disappears from the accepted chain, which is why waiting matters most for large amounts. An attacker attempting a double-spend would need to control enough of the network's mining or staking power to rewrite several blocks, and the cost of doing so rises steeply with every confirmation. Waiting is simply buying security with time.

How many confirmations are enough depends on the chain, the amount, and who is receiving it. Bitcoin exchanges commonly require three to six confirmations, with six being the traditional standard for large deposits, because six blocks represent about an hour of work that is impractical to rewrite. Ethereum deposits often need around twelve to thirty confirmations, which sounds like more but takes only minutes given its block speed. Smaller chains and Layer 2 networks have their own standards, often expressed as finality time rather than a block count.

For everyday users, the practical rule is to follow the receiving service's requirement rather than inventing your own. If an exchange says it needs six confirmations, your deposit will show as pending until then, and contacting support will not speed it up. For transfers between your own wallets, one or two confirmations are usually enough to confirm the transaction went through, though waiting longer costs nothing and adds certainty for large amounts.

Two misunderstandings are worth clearing up. First, a transaction with zero confirmations is not the same as a completed payment: it is sitting in the mempool, the waiting area for unconfirmed transactions, and it can be delayed, replaced, or dropped if fees are too low. Second, confirmations do not protect you from sending to the wrong address or falling for a scam; they only protect the transaction's place in the chain. Once confirmed, a crypto transfer is effectively irreversible, so double-check the address before sending, not after.

Some newer chains claim instant or near-instant finality, meaning a transaction is considered irreversible within seconds rather than after many blocks. That is a genuine design difference, usually achieved with different consensus mechanisms, but it does not remove the need to check the receiving service's policy. Finality is a property of the chain; crediting is a policy of the service, and the two do not always match.

In short, confirmations are the blockchain's way of turning a claim into a fact, one block at a time. Small amounts and trusted recipients need few; large amounts and exchanges need more; and no number of confirmations fixes a wrong address. Wait for the required count, confirm the transaction on a block explorer, and only then treat the payment as done.