How Long Do Crypto Swaps Take? Confirmation Times by Asset
Bitcoin confirms in 10–60 minutes; Solana in under 30 seconds. Here's what drives those gaps and how to tell a slow swap from a stuck one.
A Bitcoin swap under normal conditions takes 10–60 minutes. A Solana swap is done in under a minute. The difference isn't a quirk of any exchange — it reflects the fundamental speed gap between proof-of-work and modern consensus networks.
Understanding what drives confirmation times helps you set realistic expectations before you send, recognize when a delay is normal versus when something is stuck, and choose the right assets for time-sensitive situations. This guide breaks down the two on-chain phases every swap goes through, the typical windows for major networks, what causes congestion delays, and how to read the timeline on a fixed-rate swap before the rate expires.
What Happens Between "Confirm" and "Received"
Every swap involves two separate on-chain transactions: one on the network you're sending from, and one on the network delivering the asset you receive. Both must confirm before the swap is complete.
When you initiate a swap, the exchange service broadcasts your outbound transaction to the first network. That transaction must reach a minimum number of confirmations — a threshold that varies by exchange and by the asset's risk profile — before the service releases the inbound send. The inbound transaction then propagates across the second network and goes through its own confirmation process.
The total wait time is the sum of both confirmation windows, and the slower of the two networks sets the pace. A BTC→ETH swap requires Bitcoin to confirm first (10–60 minutes for 1–3 confirmations), then Ethereum to confirm (under 5 minutes). Bitcoin dominates the timeline almost entirely. A Solana→Bitcoin swap flips the dynamic: the SOL leg settles in seconds, and then Bitcoin takes the full window.
Some exchanges require more confirmations for large amounts. A small BTC swap might proceed after 1 confirmation; a larger one might require 3 or 6. This is intentional — more confirmations reduce the probability of a chain reorganization that could invalidate the transaction.
Typical Confirmation Times by Network
| Network | Time per block | Confirmations required | Typical total wait |
|---|---|---|---|
| Bitcoin | ~10 minutes | 1–3 | 10–30 minutes |
| Monero | ~2 minutes | 10 | ~20 minutes |
| Litecoin | ~2.5 minutes | 3 | 7–10 minutes |
| Ethereum | ~12 seconds | 12–20 | 3–5 minutes |
| BNB Smart Chain | ~3 seconds | 15 | ~1 minute |
| Tron | ~3 seconds | 20 | 1–2 minutes |
| Avalanche | ~2 seconds | 1 | < 30 seconds |
| XRP Ledger | 3–5 seconds | 1 | < 30 seconds |
| TON | < 1 second | Finalized in ~5s | < 30 seconds |
| Solana | ~0.4 seconds | Finalized in ~30s | < 1 minute |
These figures apply to uncongested networks with fees set at the standard market rate. Bitcoin and Monero stand out: both are proof-of-work chains where probabilistic finality requires waiting for multiple 2-minute or 10-minute blocks before the transaction is effectively irreversible. Most modern chains use deterministic or BFT-style consensus that reaches finality in seconds.
Exchanges typically set higher confirmation thresholds for larger swap amounts. A $50 BTC swap might clear after 1 confirmation. A $10,000 swap on the same exchange might require 3 confirmations. Check the platform's confirmation requirements if you're moving a large amount with a time constraint.
Why Delays Happen
On-chain confirmation windows are averages, not guarantees. Three common causes extend the actual wait beyond the table above.
Mempool congestion. Every transaction waits in a mempool — a staging queue of unconfirmed transactions — before a miner or validator includes it in a block. When demand spikes, the queue fills. Miners on Bitcoin prioritize by fee rate (satoshis per virtual byte), so transactions with fees set too low during a congestion event wait longer than those with competitive fees. During a high-activity period, a Bitcoin transaction with a low fee can sit unconfirmed for several hours.
Fee estimation timing. On variable-fee networks like Bitcoin and Ethereum, the exchange sets the transaction fee at the moment of broadcast. If the network gets more congested shortly after, the transaction's relative priority in the queue drops as higher-fee transactions arrive. The fee estimate made at broadcast time may no longer be competitive minutes later.
Network-level events. Hard fork transitions, validator downtime incidents, and congestion from large token launches occasionally slow block production or spike mempool activity. These are temporary and resolve without user action.
For most swaps, the network-level waiting time matches the table. Mempool congestion extending a Bitcoin swap to 90 minutes happens during busy periods; a swap taking more than 3 hours with zero on-chain confirmations warrants a support ticket.
How Fixed Rates Interact With Confirmation Time
Fixed-rate swaps lock your exchange rate for a set window — typically 10–30 minutes — to guarantee the output amount at the time you confirm. If the outbound transaction doesn't confirm on-chain before the rate expires, the exchange must ask whether you want to continue at the new market rate or receive a refund.
Bitcoin's confirmation window and a fixed-rate timer can converge. If Bitcoin is running at a normal 10-minute block time and your transaction gets included in the next block, the rate window survives. If mild congestion pushes the wait to 20–25 minutes, you may see the countdown appear on the order page before the swap finishes.
To reduce the conflict risk:
- Check whether a fixed or floating rate actually matters for the pair. For a BTC→stablecoin swap, a floating rate exposes you to minimal variance over a 20-minute confirmation window in calm conditions. Fixed rate makes more sense when the output asset is also volatile and you need to guarantee the exact amount.
- Initiate the swap only when you're ready to send immediately — the rate clock starts when the quote is generated, not when you broadcast.
- When a countdown timer appears on the order page, the rate window is closing. If the outbound transaction hasn't confirmed yet, the outcome depends on the platform's rate-expiry policy.
You can swap Bitcoin on Zest — the order flow shows the rate type and the lock window before you confirm the transaction.
When to Wait and When to Contact Support
Most delays resolve without intervention. Use this reference to decide when to act:
- Bitcoin, 0–30 minutes, 0 confirmations: Normal. Look up your transaction hash on a block explorer to confirm it's in the mempool and pending. If it appears, it will confirm.
- Bitcoin, 30–90 minutes, 0 confirmations: Possible mild congestion. The transaction is almost certainly queued and will confirm — compare the fee rate on the block explorer against current mempool minimums.
- Bitcoin, over 3 hours, 0 confirmations: The fee may be too low for current conditions. Contact support with the transaction hash. The exchange controls the sending wallet and may be able to apply a replace-by-fee bump.
- Ethereum, 0–10 minutes: Normal. Under 5 minutes is typical.
- Ethereum, over 30 minutes: Unusual. Check the transaction status on a block explorer — "pending" means it's queued, "failed" means it dropped and needs support attention.
- Solana, XRP, TON, BSC: Under 2 minutes is standard. Over 5 minutes warrants checking the transaction hash.
Always save your transaction hash (txid) when initiating a swap. It's the primary reference for block explorer lookups and support tickets. The order confirmation page contains it, and most exchanges include it in the confirmation email.
A delayed transaction is almost never a lost transaction. Bitcoin transactions that fail to confirm within 72 hours typically drop from the mempool and the inputs return to the sender's control. Ethereum transactions that stall stay pending until included in a block or dropped by the node. In either case, the transaction hash connects everything: the exchange's order, the blockchain record, and any support conversation.