How does an exchanger handle SOL deposits when the Solana network is congested

05 September 2026

The exchanger waits. It does not credit your deposit or proceed with the swap until the Solana network confirms the transaction with finality. Congestion does not change the rules - it only delays the process.

Here is why. When you send SOL to the exchanger’s deposit address, the exchanger’s software monitors the Solana ledger for an incoming transaction that matches your swap request. During network congestion, transactions may take minutes or hours to be included in a block. The exchanger cannot safely assume a pending transaction will land. It must wait for a confirmed block containing your deposit, with enough subsequent confirmations to treat the transaction as final. Only then does it mark the deposit as received and begin the outbound transfer on the destination chain.

The exchanger does not use Solana’s "processed" or "confirmed" status as sufficient. It waits for "finalized" status - the point at which a supermajority of validators have committed the block. This is standard practice. Without it, the exchanger would risk crediting a swap for a transaction that later gets dropped or reorganized out of the chain, which would mean losing the deposited SOL.

Network congestion can cause other problems. The fee you attached to the deposit transaction may become too low for validators to prioritize. If the network is backlogged, transactions with minimal fees can sit unconfirmed for hours or eventually expire. The exchanger has no control over this. It will not bump your fee or resubmit your transaction. You are responsible for choosing a priority fee that is appropriate for current network conditions. If your deposit never confirms, the exchanger never sees it, and the swap never starts.

The exchanger will also not credit deposits that arrive after the swap request’s time limit expires. Many swap requests carry a timeout - often 30 minutes to a few hours - during which the deposit must be confirmed. If congestion delays your deposit beyond that window, the swap request is cancelled. The exchanger will not hold the request open indefinitely. You would need to start a new swap, with a new deposit address, after congestion eases.

What about the outbound leg? Congestion on Solana also affects the exchanger’s ability to send SOL or Solana-based tokens back to you if the swap destination is Solana. The exchanger faces the same queuing problem. It will submit the outbound transaction with a reasonable fee and wait for confirmation. If the network remains congested, the outbound may be delayed as well. The exchanger does not prioritize your swap over others; it processes in order of confirmed deposits.

For swaps that move Solana tokens to another chain, the outbound leg is on the destination chain, not Solana, so Solana congestion only affects the deposit step. But if you are swapping tokens into Solana, both legs - the inbound deposit of the source-chain token and the outbound transfer of SOL or a Solana-based asset - are subject to the destination chain’s congestion. The exchanger’s handling is symmetric: it waits for finality on each chain before proceeding.

If you are moving assets between chains using an exchanger rather than a DEX, you should check current Solana network status before submitting a swap. The exchanger’s interface may display a warning if the network is congested, but it cannot guarantee fast confirmation. You can also choose to wait for quieter periods.

For more context on how these swaps work in general, see the hub page: Swapping Solana tokens without a DEX. It explains the overall flow of moving assets across chains and why the exchanger’s role differs from using a decentralized exchange directly.

Back to order types