Why Your Cross-Chain Swap Is Still Pending

Two is the number of networks a cross-chain swap must coordinate, and that split is why your swap can remain pending after you send it. One network records the asset you spend; the other must record the asset you receive. Your wallet may show only the first leg, while the route still has work to do.

What does “pending” mean in a cross-chain swap?

“Pending” means some step in the route has not finished or has not yet been reflected in the app you are checking. It does not always mean the same transaction is stuck: the source transaction may be waiting for confirmation, or the destination leg may still need to execute.

A route commonly involves a source-chain transaction, a service or relayer that observes it, and a destination-chain transaction. A relayer is a service that carries information or instructions between steps; the swap may depend on it before the destination network can process the transfer. For a closer look at how the steps fit together, read this fuller explanation of ParaSwap and a cross-chain route.

Which part of the route is holding it up?

Check the transaction record on the source network first. If it is still pending there, the destination step generally cannot proceed; if it failed, the route may have stopped before your asset was moved as intended. When the source transaction is confirmed, look for a destination transaction or a route status that says the transfer is still processing.

The exact labels differ by wallet and route, but the useful distinction is between a transaction that has not confirmed and one that has confirmed while a later step remains incomplete. Check these details:

• The source transaction status and its network.
• The destination network and the address set to receive the funds.
• Any destination transaction hash or route status shown by the swap interface.
• Whether the route reports a failure, refund, or action you need to take.

A block explorer, which displays a network’s public transaction records, can help you verify whether a transaction is confirmed or failed. Make sure you are looking at the correct network: the same wallet address can appear on multiple chains, but their transaction histories are separate.

What should you do while it is pending?

Use the status of the last completed step to decide what to do next. If the source transaction is still pending, wait for its status to change; if it failed, check the wallet or route interface for the failure reason before starting again. If the source transaction confirmed but there is no destination update, check the route interface for a transaction hash or recovery instructions.

Avoid submitting the swap again just because one screen has not refreshed. A second attempt could create a separate transaction and spend more funds. If the route offers a recovery or refund process, follow its instructions for that specific transaction rather than sending assets to an address supplied in an unsolicited message.

In short, identify the last confirmed step, then check the next one. “Pending” is a status, not a diagnosis; the source and destination records show where the route stands.