Why a Cross-Chain Swap Can Wait After Your Wallet Says Sent

A cross-chain swap can remain pending after your wallet reports “sent” because that confirms submission, not delivery on the destination chain. The transfer may still need confirmation on the source chain, processing by a bridge or relayer, and a separate transaction that delivers or swaps the funds on the destination chain.

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

“Sent” usually means your wallet submitted a transaction to the source network. Check that transaction’s status on an explorer for that network: a pending transaction has not yet been confirmed, while a confirmed transaction shows the source-chain step completed.

That confirmation does not prove the destination step has happened. Across’s documentation, for example, tracks a deposit from its source transaction through a relayer fill, with states such as pending, filled, expired or refunded. Other bridges use different steps and status labels.

Why does the destination transfer take longer?

After the source transaction confirms, a bridge may wait for network confirmations, verify the transfer, then arrange execution on the destination chain. Some systems use relayers to advance funds before a later settlement; others follow different mechanisms, so timing depends on the route and protocol.

A cross-chain swap can also include a token swap after bridging. LI.FI’s documentation treats cross-chain transfers and destination-chain swap steps as distinct parts of a route. If that final step stalls, the bridge may have delivered the funds while the requested output token is still pending.

What should you check while it is pending?

Use the transaction hash and the bridge’s own tracker to locate the transfer’s current step. A wallet’s activity screen may show the source transaction without showing a later destination transaction, so check the destination explorer and the recipient address as well.

• Confirm the source transaction succeeded on its own network.
• Check the bridge tracker for a pending, completed, expired or refunded status.
• Verify the destination network, token and recipient address before treating the swap as complete.

When is a QuickSwap route the issue?

QuickSwap route selection matters when the swap itself is taking place on a supported chain; it does not explain every delay in a cross-chain transfer. If the bridge step is complete but the token swap stalls, see this guide to choosing a QuickSwap route after a stall for route-specific detail.

The practical rule is to follow the transaction across both networks: “sent” marks the start, source confirmation marks one completed step, and destination delivery marks the outcome.