How many confirmations does each blockchain wait for before a swap settles

07 September 2026

Confirmations vary by chain, and the number is set by the exchanger, not the blockchain itself. There is no single universal figure, but the common ranges are: Bitcoin typically waits 1 - 3 confirmations, Ethereum and most EVM chains wait 1 - 2, and faster chains like Solana or Tron often wait 0 - 1. The exact count depends on the asset you send and the risk the exchanger is willing to take.

The reason is simple. A confirmation is one block added on top of the block that contains your transaction. Each new block makes it harder for someone to rewrite history and double-spend the coins they just sent you. The exchanger wants to be sure the incoming payment is final before it releases the outgoing side of the swap. Wait too few blocks, and a reorg could reverse the deposit; wait too many, and you sit staring at a pending screen for no good reason.

Here is the practical breakdown. Bitcoin, because its blocks come every ten minutes on average and its hash rate is enormous, is the slowest to confirm. One confirmation for a small swap is common, but many services require three for larger amounts. The cost of a reorg on Bitcoin is astronomical, so one block is usually enough for small sums. Ethereum’s blocks arrive every twelve seconds, so waiting for two confirmations takes under half a minute. That is why most EVM swaps settle in under a minute once the transaction is in a block. Polygon, Arbitrum, and other L2s have blocks every couple of seconds, so even three confirmations are trivial. Solana finalises in under a second, and some exchanges accept a swap with zero confirmations because the chain’s proof-of-history makes reorgs extremely unlikely. Tron sits in a similar bucket, though its block time is three seconds, so one confirmation is standard.

The number also scales with the amount. A $20 swap gets fewer confirmations than a $20,000 swap. That is not a policy quirk; it is arithmetic. The cost of a double-spend attack on a chain is roughly fixed, so the risk is proportional to the value moving through it. Small payments are not worth attacking, so the exchanger shortens the wait. Large payments justify a few extra blocks to be safe.

One more factor is congestion. Confirmations are not the only delay. If the mempool is full and your fee is low, your transaction might sit unconfirmed for hours before the first block even includes it. The confirmation count only starts ticking after that. So a 1-confirmation Bitcoin swap can take two hours if the network is jammed, while a 3-confirmation Ethereum swap on a quiet day is done in thirty seconds. The number of confirmations is a ceiling on risk, not a promise of speed.

What should you do while it runs? Do not resubmit. Sending the same coins twice, or bumping the fee on a stuck transaction, can create a double-spend that the exchanger reads as a failed deposit. Just wait. Most swaps have a status page that shows the exact confirmation count required for your pair. Watch that, not the block explorer’s raw numbers, because the exchanger’s threshold may differ from what the chain recommends.

If you want the full picture of why a swap feels slow, including network congestion, fee markets, and the exchanger’s own internal delays, the hub page "Why your swap is still pending and what actually speeds it up" is the next thing to read. This page only answers the confirmation part of the puzzle. The rest is separate.

Back to card purchases