Diagnose a stalled cross-chain swap by its execution step

A stalled cross-chain swap is easiest to diagnose by identifying whether it stopped at route selection, source-chain execution or destination-chain delivery. A quote describes a proposed path: one or more swaps, a bridge transfer, or both. It does not prove that funds have moved. Start with the transaction hash and the route details shown by the swap interface, then check each completed step before trying again.

How does cross-chain route discovery work?

Route discovery searches for a sequence of supported actions that can move the input asset on the source chain into the requested asset on the destination chain. A route can include a source-chain swap, a bridge, and a destination-chain swap. The available paths depend on token support, bridge support, liquidity, amount limits and the assets each step can accept or deliver.

A quote is a time-sensitive estimate of that path. Its output can account for trading fees, bridge fees, price impact and gas, but the exact fields vary by provider. A route with a higher estimated output may take more steps or rely on different liquidity than a shorter route. Compare the expected destination asset and minimum output as well as the estimated amount; the cheapest-looking path is useful only if it meets the swap’s actual requirements.

The key routing question is what asset must arrive at each handoff. A bridge may accept one token and deliver another, or deliver a token that needs another swap before it matches the requested output. This fuller explanation of Paraswap bridge routes and the asset that needs to arrive covers that distinction in more detail. A route that is unavailable may reflect a missing token or chain combination, insufficient liquidity, or a provider limit; it does not by itself show that the swap interface is broken.

What should I check when a swap stalls?

Check the transaction and route step that last changed state; the word “pending” alone does not identify the cause. Find the source-chain hash in the swap interface or wallet and open it in an explorer for that chain. For EVM transactions, the receipt shows whether the transaction was included successfully or reverted. If it has not been included, the bridge step has not yet had a confirmed source transaction to process.

• No source transaction hash: Check whether the wallet still needs a signature, whether a token approval is a separate step, or whether the quote expired before submission.
• Source transaction pending: Check its status on the source chain. If the wallet offers a speed-up or replacement, understand that action through the wallet’s own flow before using it; behavior depends on the chain and transaction.
• Source transaction reverted: Read the explorer’s failure details and check whether the route’s approval or execution step failed. On EVM chains, a reverted transaction does not complete its on-chain state changes, though the transaction can still consume gas.
• Source transaction succeeded, destination absent: Check the route provider’s tracker or status endpoint using the source hash. Look for a destination transaction, a pending delivery state, or an explicit action required from the user.

Approval and swap are different transactions when the token allowance has not already been granted. An approval permits a contract to spend a token up to a specified allowance; it does not execute the swap or bridge transfer. If the interface requested approval first, confirm that approval succeeded, then check whether the separate swap transaction was submitted.

When should I refresh the route or submit again?

Refresh the quote before submission if it has expired, its terms have changed, or the interface reports that the route is no longer available. A new quote may choose a different path because liquidity, prices or provider availability changed. Compare the chain, token contract addresses, amount, destination address and minimum output again before signing.

After a source transaction succeeds, do not submit the same swap again just because the destination wallet has not updated. First establish whether the selected bridge or route has recorded the source transfer and whether it has created a destination transaction. Some routes deliver through a liquidity provider; others depend on a message or another protocol-specific process. The next step and expected timing therefore depend on the route shown in the original quote, not on a universal bridge rule.

If the route tracker reports a failed delivery or a recovery action, use the instructions for that specific route and verify that the page corresponds to the provider and transaction you used. If it shows only that the source step succeeded, that is not proof of destination delivery. A wallet balance can also lag behind a completed transaction, so check the destination chain and token contract rather than relying only on the displayed token name.

The practical rule is to retry only after locating the last completed step and establishing that no further action is already in progress. Confirmed means the relevant chain recorded the transaction or event. Unverified means the destination asset has not been confirmed in the wallet or on the destination chain, regardless of what the quote predicted.