Why does a SOL swap show as completed on Solana but not on the destination chain

05 September 2026

The swap shows as completed on Solana because the exchanger has received your SOL and confirmed it on the Solana ledger. It has not yet appeared on the destination chain because the exchanger still needs to send the corresponding tokens on that chain, and this second step can take minutes to hours depending on network conditions, liquidity, and the exchanger's internal processing.

Here is the core reason: a cross-chain swap is not a single transaction. It is two separate transactions linked by the exchanger's system. The first transaction is your SOL transfer to the exchanger's Solana address. The second is the exchanger's outbound transfer to you on the destination chain. Solana confirms the first transaction quickly - often in under a second. The destination chain's confirmation is a separate event. Your wallet or block explorer on Solana has no direct view of the destination chain's state. It only sees that your SOL left your wallet and arrived at the exchanger. That is why the swap appears "complete" on one side but not the other.

Several factors can delay the second transaction. Solana's speed works against your expectations here. A user who sends SOL sees it confirmed almost instantly. The exchanger's software then needs to detect that deposit, match it to your order, check the current rate, and initiate the outbound transfer. This detection and matching step is not instantaneous. Exchangers batch or queue transactions to manage risk and liquidity. If the destination network is congested - Ethereum during a gas spike, for example - the exchanger may wait to send until fees are reasonable or until it can bundle your transfer with others. Some networks require a minimum number of confirmations before the exchanger considers a deposit safe. Solana's finality is fast, but some exchangers still wait for extra blocks out of caution.

Another common cause is a mismatch in the memo or destination address. If the destination chain requires a memo or tag (common on Binance Smart Chain for some tokens, or on the Stellar network), and you omitted it, the exchanger cannot automatically route the funds. The transaction on Solana completes. The funds sit in the exchanger's pool. You may need to contact support to provide the missing information. The swap will then show as stuck on the destination side, even though Solana's ledger shows a successful send.

The exchanger also needs to maintain a reserve on the destination chain. If it runs low on the token you requested, it must acquire more before sending to you. This internal rebalancing adds time. You will see the SOL deposit confirmed, but the outbound transaction may not appear for minutes or hours.

If you are reading this page, you are likely using an exchanger rather than a DEX for moving SOL and Solana-based assets in and out of other chains. That hub page explains the trade-offs: an exchanger handles the cross-chain logic for you, but you surrender control over timing. The swap completes on Solana first because that is the fast leg. The destination leg moves at the pace of the slower network and the exchanger's own workflow. If more than an hour has passed and the destination chain shows no pending transaction, check the order status on the exchanger's site or contact its support with the Solana transaction ID. Do not assume the funds are lost. The Solana confirmation is usually the easy part. The wait is for the rest of the journey.

Back to order types