kendra-koepp

What Happens When Your Cross-Chain Swap Gets Stuck?

When a cross-chain swap stalls, one of its two on-chain legs may still be waiting: the source-chain transfer or the destination-chain delivery. That can leave the swap pending even after you see a successful transaction on the first chain.

Why can a cross-chain swap stay pending?

A cross-chain swap usually has several steps: your source-chain transaction moves the asset, the bridge or service waits for enough confirmations, and a destination-chain transaction delivers or swaps the funds. Those steps do not settle at the same instant. A slow block, network congestion, or extra confirmation requirements can stretch the wait.

A successful source transaction means the network accepted that transaction; it does not by itself prove that the destination transfer finished. The service may still need to verify the source-chain event and relay a message or proof to the destination chain. Some routes also need a separate destination transaction to complete the swap.

For example, someone moving ETH from one chain to BNB Smart Chain and swapping into a destination token may see the source transfer confirmed while the destination swap is still processing. In that case, the key question is whether the destination transaction has been submitted, not simply whether the first transaction succeeded.

How do you tell a delay from a failed swap?

Start with the source transaction hash in that chain’s block explorer. Check its status and whether it has enough confirmations for the route. A reverted transaction is a failure: the transfer did not complete, though the sender may still pay gas. A confirmed transaction is evidence that the source leg completed, but you still need to check for a destination-chain transaction or delivery.

Use the transaction hash or route reference to trace the same transfer on the destination chain. If there is no destination transaction yet, the transfer may still be awaiting verification or relay. If a destination transaction exists, check whether it succeeded, reverted, or is still pending. A destination revert can require a route-specific recovery action; the funds do not necessarily return automatically.

One edge case is a source-chain reorganization, where a recent block is replaced and a transaction that looked confirmed disappears from the canonical chain. That is why services may wait for multiple confirmations before acting. If the source transaction is no longer confirmed, treat the earlier status as provisional and do not assume the destination leg will arrive.

What should you do next?

Match the source and destination records before taking action. Confirm the source transaction hash, the asset and amount sent, and the destination address and chain. Then look for a destination transaction tied to that transfer. Do not start a second swap while the first transfer may still be in flight; you could commit the same funds twice.

  • Source transaction reverted: the transfer did not complete; check your balance and account for gas before trying again.
  • Source transaction confirmed, no destination record: keep the hash and route details, and check the service’s stated processing status.
  • Destination transaction reverted: check whether that route offers a claim or refund process before sending anything again.
  • Both legs show success: check the destination wallet and token details; the received asset may differ from the one sent.

If the original transfer is confirmed as failed or fully recovered, you can plan a replacement transaction. ParaSwap can move crypto across chains and swap it into a destination asset in one flow, which is useful when the next step is to bridge and swap again. Before resubmitting, verify that the first route no longer has funds in transit.

ParaSwap is relevant when you need that new cross-chain move, but it cannot make an earlier pending transaction settle faster. Keep the original hash and compare the two chains’ records so you do not confuse a new transfer with recovery of the old one.

Questions to check before retrying

Does a confirmed source transaction mean the swap is complete?

No. It means the source-chain leg was accepted and recorded. The bridge or service may still be waiting for confirmations, relaying a message, or executing the destination transaction. Check the destination chain for a transaction tied to the same transfer before treating the swap as complete.

Can I cancel a pending cross-chain swap?

Usually, a confirmed source-chain transaction cannot simply be cancelled like an unsubmitted transaction. What happens next depends on the route: it may complete later, or a failed destination step may have a recovery path. Check the transaction status and route instructions before attempting any cancellation or replacement.

Why did the destination transaction fail?

Destination execution can fail because conditions changed after the source transfer, such as insufficient liquidity or a contract error. The exact cause should appear in the destination transaction record. A failed destination transaction does not always mean the source funds are lost, but any refund or claim depends on the route’s design.

What information should I keep while waiting?

Keep the source transaction hash, destination chain and address, asset and amount, and any route reference. These details let you compare the two chains and identify the transfer if you need to follow its status. The practical rule is simple: verify the source and destination legs before you retry.