What to Do If Your Cross-Chain Swap Is Stuck
If your cross-chain swap looks stuck, start here: check whether your source-chain transaction actually confirmed on a block explorer, check the bridge or aggregator’s own status page or transaction history for a pending claim step, and confirm you hold enough native gas on the destination chain. Most “stuck” swaps aren’t lost; they’re waiting on a finality period, a relayer step, or a manual claim action you haven’t completed yet, and they resolve within minutes to a few hours. Genuinely lost funds from a stuck swap are rare when using an established route; the far more common outcome is a delay, not a loss.
Why Cross-Chain Swaps Get Stuck
A cross-chain swap isn’t one transaction, it’s a sequence of steps across two (or more) blockchains, and “stuck” usually means one specific step in that sequence hasn’t completed yet, not that anything has failed or been lost.
Finality delay. The destination chain typically won’t credit funds until the source chain’s transaction is considered final, meaning enough subsequent blocks have been added that the transaction is extremely unlikely to be reversed. This is the single most common reason a swap looks stuck, and it resolves on its own; you’re waiting, not stuck in the sense of needing to act.
Relayer or bridge processing time. Most cross-chain routes depend on an off-chain relayer, validator network, or bonder to detect your source transaction and submit the corresponding action on the destination chain. This step can take anywhere from a few minutes to a couple of hours depending on the specific bridge and current network conditions, and a backlog during high network activity can extend that window further.
A pending manual claim. Some bridges require you to sign a separate transaction on the destination chain to actually receive your funds, rather than delivering them automatically. If that claim step exists and hasn’t been completed, the transfer will sit in a pending state indefinitely until you take that action yourself.
Insufficient gas on the destination chain. If your wallet doesn’t hold enough of the destination chain’s native token to pay for a claim transaction or the final leg of the swap, that step can’t execute even once everything upstream has completed.
Rollup withdrawal challenge periods. For transfers involving certain Layer 2 networks specifically (withdrawals from some optimistic rollups back to a base layer), a multi-day challenge period is part of the normal, by-design security model, not a malfunction. A withdrawal sitting pending for several days on one of these specific routes may be on schedule, not stuck at all.
Step-by-Step: What to Check
- Confirm your source transaction is actually finalized. Look up the transaction hash on the block explorer for the source chain and confirm it shows as confirmed, not pending or failed. If it’s still pending, the problem is upstream of the bridge entirely, and the fix is different (see below).
- Check the bridge or aggregator’s transaction status directly. Most bridges and swap aggregators provide a status page or transaction history where you can paste your transaction hash and see exactly which stage the transfer is in, waiting for finality, waiting for a relayer, or ready for a manual claim.
- Check the destination chain explorer for an incoming transfer. Search your destination wallet address directly to see if funds have already arrived, sometimes a transfer completes before the front-end interface has updated to reflect it.
- Look for a claim, redeem, or finalize button. If the bridge’s interface shows a pending transfer with an available claim action, that’s very likely the fix: complete that step yourself rather than continuing to wait.
- Confirm you have native gas on the destination chain. If a claim step is required and you don’t hold the destination chain’s gas token, acquire a small amount before attempting the claim.
- If your source transaction itself is stuck pending, don’t resend. If the original transaction hasn’t been confirmed at all, the fix is a speed-up or replacement transaction using the same nonce with a higher gas fee, not sending a second, separate transaction. Sending again can create a duplicate that complicates recovery rather than resolving the original delay.
When It Resolves Itself vs. When You Need to Act
Resolves on its own: waiting for source-chain finality, waiting for a relayer during normal network conditions, and rollup challenge periods that are functioning as designed. In these cases, the transfer is progressing correctly; the correct action is to wait and check back rather than to intervene.
Needs your action: a pending manual claim step, insufficient destination-chain gas preventing a final step from executing, or a source transaction stuck pending due to an underpriced gas fee. In these cases, waiting indefinitely won’t resolve anything, since the process is paused on a step only you can complete.
Needs official support: a transfer that’s been pending well beyond the bridge’s typical timeframe with no claim option available and no clear status update, or any situation where the standard checks above don’t explain what’s happening. At that point, contact the bridge or platform’s official support channel directly, through their verified website or documented support process, with your transaction hashes ready.
A Scam Warning Worth Taking Seriously
Searches for “stuck swap” or “bridge transaction pending” are a known target for scams. Fraudulent posts and fake support listings sometimes appear specifically in this search space, offering a phone number or chat link to “recover” your funds. Never share your seed phrase or private keys with anyone claiming to help unlock a stuck transaction, no legitimate support process requires it, and never interact with a “claim” link received via DM or an unsolicited message. Use only the official bridge or platform interface, or a support channel you’ve verified directly through the project’s own website.
How to Avoid It Next Time
Test a small amount on a new route or bridge before committing a large transfer, particularly for a chain pair you haven’t used before. Keep a small buffer of native gas on the destination chain ahead of time, rather than needing to acquire it mid-transfer. Where possible, use a routing tool that shows clear, real-time status for each leg of a cross-chain swap rather than a single opaque “pending” state, so you can see exactly where a transfer sits without needing to manually check multiple explorers yourself.
FAQ
Why is my cross-chain swap stuck?
Most commonly, it’s waiting on source-chain finality, a relayer processing step, or a manual claim action on the destination chain that hasn’t been completed yet. These are normal parts of how cross-chain transfers work, not failures, and the large majority resolve within minutes to a few hours.
How long should a cross-chain swap take?
It varies by route and current network conditions, from a few minutes for fast, well-liquidated routes to a few hours for routes requiring more confirmations or relayer processing. Withdrawals from certain Layer 2 rollups back to a base chain can intentionally take several days as part of their security design, which is different from a genuinely stuck transfer.
Can I get my funds back if a swap fails?
In most cases, yes. A source-chain transaction that confirms but a destination-chain step that fails typically has a documented recovery path, a manual claim, a retry function, or a timeout that automatically returns funds, depending on the specific bridge’s design. Genuine, permanent loss is uncommon on established routes; it’s far more common for a transfer to be delayed or paused on a step you can complete than to be lost outright.
How do I avoid stuck swaps?
Test small amounts on new routes before large transfers, keep destination-chain gas available ahead of time, and use routing tools that provide clear status visibility across each leg of the transfer rather than a single undifferentiated pending state.
Get Started
For programmatic access to cross-chain routing with transaction status tracking, see the YiFi Swap API documentation.
For a broader explanation of how bridges and cross-chain aggregators work mechanically, see Cross-Chain Swaps Explained. For the full method on minimizing risk on large cross-chain trades, see How to Execute Large Crypto Swaps With Minimal Market Impact.