How long does each step of a cross-chain swap take from deposit to final receipt

05 September 2026

The total time from deposit to final receipt in a cross-chain swap typically ranges from a few minutes to over an hour, depending almost entirely on the blockchains involved and their confirmation requirements. No single step takes a fixed duration; each one depends on network congestion, the number of confirmations required, and the swap mechanism used.

Here is the breakdown of each step, with realistic time ranges and the reasons behind them.

Step 1: You send the deposit transaction (1 - 30 seconds for broadcast)

Once you click "send" on your wallet, the transaction must be broadcast to the network and included in a block. On fast chains like Solana, this can happen in under a second. On Ethereum or Bitcoin, it may take 10 - 30 seconds during normal conditions. If the network is congested, you might wait minutes for inclusion, regardless of the fee you set.

Step 2: The exchanger waits for confirmations (variable, often 1 - 60 minutes)

This is the longest and most variable step. The exchanger does not credit your deposit after a single block; it waits for a number of confirmations that reduces the risk of a chain reorganization or double-spend. The exact number depends on the chain:

• Bitcoin: typically 2 - 6 confirmations, each taking ~10 minutes. That means 20 - 60 minutes.
• Ethereum: often 12 - 30 confirmations, each ~12 seconds, so 2 - 6 minutes.
• Solana: usually 1 - 2 confirmations, each ~0.4 seconds, so under a second.
• Polygon, BNB Chain, Avalanche: similar to Ethereum, 1 - 5 minutes total.

The exchanger sets these thresholds based on its own risk tolerance. You cannot speed this up by paying a higher fee after the deposit is sent.

Step 3: The exchanger processes the swap internally (seconds to a few minutes)

Once the deposit is confirmed, the exchanger must lock in the exchange rate, determine the destination address (including any memo or destination tag you provided), and prepare the outgoing transaction. This is purely server-side work and usually takes seconds. Delays here are rare and usually indicate a queue of other swaps being processed.

Step 4: The exchanger sends the outgoing transaction (1 - 30 seconds for broadcast)

The exchanger broadcasts the transaction to the destination blockchain. Same variability as Step 1, but now on the destination chain. The recipient's wallet will see the transaction pending almost immediately.

Step 5: The destination chain confirms the receipt (variable, same pattern as Step 2)

The receiving wallet or exchange will typically require a certain number of confirmations before it shows the funds as "received." If you are sending to a centralized exchange, it may require 30 - 60 confirmations on Ethereum or 2 - 4 on Bitcoin. If you are sending to a personal wallet, the funds appear after the first block but are not fully safe from reorgs until the same number of confirmations the destination chain's standard requires.

Why the total time is not predictable to the minute

Every step except the internal processing is subject to network congestion. A single congested block on Ethereum can add 30 seconds. A backlog of Bitcoin transactions can push your deposit's inclusion to the next block, adding 10 minutes. The exchanger has no control over these times.

What you can do to minimize delays

• Use a blockchain with fast finality (e.g., Solana, Polygon) for the deposit or the receipt.
• Set a reasonable fee on the deposit transaction. Too low a fee means your transaction may sit unconfirmed for hours.
• Check the exchanger's stated confirmation requirements before starting. Some list them on their status page.

A note on the broader process

This page is part of a set about swapping crypto across chains without a bridge or centralised account. The mechanics of how the exchanger actually moves value between blockchains - without holding your funds in a pooled account - are covered in the sibling pages. The key takeaway here is that the time cost is dominated by waiting for block confirmations, not by the swap logic itself.

Back to staking