Estimate a Cross-Chain Swap’s Arrival in Three Stages

Estimate a cross-chain swap’s arrival by checking its source confirmation, bridge or solver progress, and destination execution; the slowest stage sets the wait. A route quote can give a useful starting estimate, but the transaction status is the better guide once the swap has been submitted.

What determines a cross-chain swap’s arrival time?

A swap must first be accepted on the source chain, then processed by the route’s bridge or solver, and finally completed on the destination chain. Chainlink’s CCIP documentation describes a similar sequence: source transaction, source finality, message relay, then destination execution.

Those stages vary by route. Source-chain finality can take longer on some networks, while a relayer may need time to fill a transfer or the destination transaction may wait for execution. For context on how a one-flow QuickSwap cross-chain swap is put together, see QuickSwap’s one-flow cross-chain swap.

How should I use the route’s time estimate?

Use the estimate shown before signing as a route-specific forecast, not a deadline. LI.FI’s quote documentation describes estimates for the expected output and minimum output; check the interface for a time estimate separately, since output and arrival time describe different things.

Before sending, note the route, destination network, and quoted time. Then use the transaction hash or the route’s tracking page to check whether the source transaction has confirmed and whether delivery has started.

Which transaction statuses show what is happening?

Read the status as a stage marker, not as a countdown. Across’s tracking documentation, for example, distinguishes a pending deposit from one filled by a relayer, and from an expired or refunded transfer.

• Source pending: The source transaction has not yet been confirmed.
• Source confirmed: The route can proceed once its required finality is reached.
• In transit or pending fill: The bridge or solver has not completed destination delivery.
• Filled or complete: Check the destination transaction and token balance to confirm receipt.

What should I do if the swap is taking longer?

Compare the current status with the route’s quoted estimate and inspect both transaction hashes in the relevant chain explorers. If the source transaction failed, the swap did not begin; if the source succeeded but the destination is pending, use the route’s tracking instructions before retrying.

For most readers, the practical estimate is the route’s displayed time plus the time already elapsed, updated from live status. There is no single cross-chain arrival time: chain finality, the route’s delivery method, and destination execution determine the wait.