Why Ethereum deposits wait for confirmations

Ethereum blocks arrive about every 12 seconds, but exchanges can wait about 15 minutes or longer before crediting a deposit. The delay gives the receiving service time to check that the transfer is in the chain it accepts and, for a stronger guarantee, that Ethereum has finalized the block.

A wallet may show a transaction as successful as soon as it is included in a block. That confirms execution on the current chain view; it does not mean every exchange has met its own crediting threshold. An exchange chooses that threshold according to its risk controls and may show a pending deposit while it waits.

What does a confirmation mean on Ethereum?

A confirmation means a transaction has been included in a block, with later blocks extending the chain after it. Ethereum.org describes blocks as batches of transactions linked by references to their parent blocks; new blocks are proposed roughly every 12 seconds.

As more blocks follow the one containing a deposit, a short-lived chain reorganization becomes less likely to remove that transaction from the chain the network settles on. This is why services often count confirmations: the count is a practical signal of how much the chain has built on top of the deposit, not a separate approval issued by Ethereum.

Confirmation counts are useful when comparing transfers across networks, but the same number does not mean the same security on every chain. For a separate guide to choosing a route for regular transfers, see how to compare Polygon Bridge routes for transfers. A bridge may also wait for source-chain checks before releasing assets on its destination chain.

Why can an exchange wait after a transaction appears?

An exchange waits because it must decide when the chance of a deposit being reversed is low enough for it to credit funds. A wallet and an exchange can therefore show different statuses: the wallet reports that the transaction was included, while the exchange is still counting blocks or waiting for a stronger settlement signal.

The cutoff varies by service and deposit type. The exchange’s deposit page or status message is the relevant guide; Ethereum itself does not set one universal confirmation count for every business. Congestion can delay inclusion before confirmation counting starts, while an exchange’s own processing can add time after the chain condition is met.

How does Ethereum finality change the wait?

Ethereum’s proof-of-stake consensus gives blocks an explicit finality status, beyond simply having newer blocks built on top. Ethereum.org says validators vote on checkpoint blocks, and a checkpoint is finalized when the required supermajority of staked ETH supports the relevant checkpoints.

Ethereum’s documentation puts typical finality at about 15 minutes. Finality means reversing a finalized block would require a major consensus failure and destruction of a large amount of stake; it is a stronger assurance than seeing a few later blocks. Services handling deposits can use their own confirmation threshold, wait for finality, or combine these signals with other checks.

For a routine transfer, treat “included,” “confirmed,” and “credited” as distinct stages. Check the receiving service’s deposit rules before sending, then use its status page to see whether the delay is on Ethereum or in the service’s crediting process.