First check whether the source-chain transaction confirmed. If it is still pending, do not submit the swap again. If it confirmed, follow the original wallet or swap service’s bridge tracker, then check the destination chain explorer before deciding funds are missing. A confirmed source transaction does not prove the destination leg completed.
How to check where a cross-chain swap is stuck
A cross-chain swap can involve a source-chain transaction, bridge processing, and a destination-chain transaction—sometimes with swap steps on either side of the bridge. Check each stage in order. A wallet’s completed or pending label, by itself, may not tell you whether the destination leg has settled.
1. Find the swap and save its details
Open the activity or history in the wallet or service that started the swap. Record the source transaction hash or signature, source and destination networks, sending and receiving wallet addresses, token symbols, amount, and approximate time. Save a screenshot of the displayed status. Circle’s USDC Bridge support also asks web users for the provider and version, browser, and operating system.
2. Check the source transaction on its chain
Open the source hash in that network’s explorer. If the transaction is pending or has not confirmed, wait rather than starting another swap. Phantom categorizes an unconfirmed source transaction as a wait state and warns that retrying can create a duplicate. Circle advises checking whether confirmations are increasing; if they are, wait and check again.
#1 Best Overall
3. If the source confirmed, check the initiating service’s tracker
Use the status link in the original swap interface or its official bridge or provider tracker. Choose the tracker for the service that initiated the route, not a generic bridge tracker. For example, Uniswap directs users to its activity tab and the Across explorer for its supported flow; Phantom directs users to LI.FI Scan for its flow.
Do not treat a countdown as a deadline. Phantom says its displayed estimate reflects bridge processing, not underlying blockchain confirmation time, and a transaction can take longer than the countdown. Uniswap Labs Support said, in guidance updated February 24, 2026, that most swaps on its service complete within a few minutes. That is a service-specific estimate, not a general benchmark for cross-chain swaps.
Rank #2
- Ideal for Gifting
- Ideal for a bookworm
- Compact for travelling
4. Check the destination chain and receiving wallet
Look for an arrival transaction on the destination chain’s explorer, then confirm that your wallet is viewing the intended network and supports the token. Uniswap notes that its interface may show a completed state before the bridged tokens are visible in the wallet. If the source confirmed but no destination transaction appears, Phantom says not to reset the wallet; contact support with the source hash and both addresses.
What a failure or recovery status means
Recovery depends on the route and the stage that failed. A returned or delivered asset may not be the token you originally sent: an intermediate token used for the bridge step may be what comes back. For example, a route that wraps ETH to WETH before bridging may return WETH; a route that first swaps ETH to USDC may return USDC. Check the recovery chain, token, and settled amount in the provider’s status details before taking further action.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Scan for outdated or missing drivers - takes under a minute3Clear out junk files and repair common Windows errors| Service or status system | Documented status or outcome | What to check |
|---|---|---|
| 0x tracking | Some failures lead to an automatic origin refund; some use a destination retry. Some providers are not tracked by this status service. | refund_pending means continue polling. refund_succeeded reports completed refund details. A retry hash alone does not prove the destination transaction mined; bridge_filled marks a successful destination retry. Verify the settled amount and chain. For a terminal failed status, contact support with the zid. |
| Polygon Trails | For its documented case of funds stuck in an intent address, the user can connect the originating wallet in transaction history or the explorer and select “abort” to sign a recovery transaction. | Use this only for the specific Trails procedure and case; it is not a general recovery step for other bridges. |
| PancakeSwap, Across route | PancakeSwap says a source-chain transaction failure returns the original token on source. For an Across bridge failure, it estimates a refund of the bridged asset on source within 90 minutes to two hours. If the destination swap fails, the bridged asset remains on destination without the final swap. | These are route-specific support statements, not universal refund promises. PancakeSwap also describes a faster Relay refund for a particular SOL-to-EVM scenario, but that should not be generalized to other routes. |
These examples are not interchangeable. A returned asset can be on a different chain or have a different token symbol than the original input. Do not retry, sign a recovery transaction, or assume a refund is due based only on a hash or a generic “failed” label; follow the exact provider’s instructions for the route and status shown.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When to contact the wallet or swap provider
Contact support through the wallet or protocol’s official website when the provider’s criteria are met. Phantom advises contacting its support if a swap on its flow is stalled or failed for more than an hour after the source transaction confirmed. That is a Phantom support threshold, not a universal bridge timeout. Circle recommends contacting Customer Care when a delay exceeds the expected time for the destination chain.
Rank #4
Have the details relevant to your service ready:
- Source hash or signature and the status screenshot.
- Sending and receiving wallet addresses, both networks, token symbols, and amount.
- Date and approximate time of the swap.
- For a 0x terminal
failedstatus, thezid. - For Circle USDC Bridge web support, the provider and version, browser, operating system, and device details requested by Customer Care.
A wallet provider may be able to escalate a case to the bridge provider, but it cannot reverse or force completion of an on-chain transaction. Follow the recovery steps the relevant provider documents for your specific route.
Quick Recap
Best Value
- It can be a gift option
- Comes with secure packaging
- Helpful in various ways
How to protect yourself while troubleshooting
- Reach support from the wallet or protocol’s official site or app. Do not trust unsolicited messages, search ads, or unfamiliar “recovery” sites as proof of legitimacy.
- Never share your seed phrase or private key with anyone claiming to recover a bridge transaction.
- Do not connect your wallet to unfamiliar token links or follow unverified claim instructions.
- Do not reset a wallet to try to make a missing destination leg appear. Verify the destination chain and token support first, and contact the provider if the destination transaction is absent after the source confirmed.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
