Why a cross-chain swap can leave your funds in limbo

A cross-chain swap can leave you waiting because it is a sequence of actions on separate blockchains, not one transaction that either completes everywhere or fails everywhere. First, your wallet sends the input token to a contract on the source chain. A bridge or relayer then arranges for value to reach the destination chain. A final swap may convert that value into the token you requested. Each step has its own transaction, fees and confirmation rules.

What happens after you start a cross-chain swap?

The route begins with a quote: the service chooses a bridge, token pair and destination amount, often using liquidity providers or relayers to make the transfer. Your wallet signs the source-chain transaction, and the source network includes it in a block. The bridge then detects that deposit and verifies it according to its design. Some bridges lock tokens on one chain and mint or release corresponding tokens on another; liquidity networks can instead have a provider pay out on the destination chain. Ethereum.org’s bridge guide describes these as distinct transfer designs.

In an intent-based route, the relayer may front the destination tokens before the bridge later settles its accounts. Across’s documentation describes this as initiation, fill and settlement: the user deposits, a relayer delivers on the destination, and the protocol verifies and repays the relayer. For a fuller comparison of route choices, see this ParaSwap cross-chain route guide for 2026. The analogy is a parcel with separate handoffs: a tracking status at one depot does not prove that the next depot has received it.

Why can one leg finish while the swap appears stuck?

Because each leg depends on a different network or service, a completed source transaction does not guarantee that the destination transaction has happened. Congestion can delay confirmations. A relayer may not fill a deposit before its deadline, or the route may need a destination-side swap that cannot execute at the quoted terms. A bridge can also take longer when its verification process requires more time. A token may have arrived but remain unseen because the wallet is displaying the wrong network or not showing that token.

Look for the stage that stopped rather than treating “pending” as one universal failure:

• Source transaction pending: Check its hash on the source-chain explorer. The bridge cannot act on a deposit the chain has not confirmed.
• Source confirmed, no destination transfer: Check the route’s tracker or bridge status. A relayer fill or message verification may still be pending.
• Destination transfer confirmed, token not visible: Switch the wallet to the destination network and verify the token contract address.
• Destination swap failed: Check whether the bridge delivered an intermediate token. The bridge leg may have completed even if the final conversion did not.

These distinctions matter because some routes are not atomic. In Across’s documented flow, an expired deposit can remain escrowed on the origin chain while a refund is processed; its documentation says refunds can take several hours. The exact recovery path depends on the bridge and route, so use that route’s status page and instructions.

What should you do if your cross-chain swap is stuck?

Start with the source-chain transaction hash and confirm whether it succeeded. Then check the bridge or swap service’s tracker for a deposit, fill, destination transaction or refund status. If a transaction failed, inspect which chain it failed on and whether any intermediate token arrived. Do not send a second transfer just because the destination wallet looks unchanged: the first route may still be processing, and a duplicate can create a second transfer rather than resolve the first.

Before signing a new route, verify the source and destination networks, token addresses, recipient address, quoted minimum output and any deadline. Keep enough of the destination chain’s native token for a separate swap or other action if the route requires one. For most users, a route with clear stage-by-stage tracking and a stated recovery path is easier to manage than one that only advertises a fast estimate. The practical rule is simple: follow the transaction through each chain, and identify the last confirmed step before acting.