If timing matters, choose a route whose current estimate fits your deadline and allow extra time for chain confirmations; a cross-chain swap can take minutes or tens of minutes, and some routes take longer. The total depends on the source and destination chains, the route’s security checks, and whether the destination transaction succeeds on its first attempt.
First, the source-chain transaction must be included in a block. The route may then wait for enough confirmations or for the chain to mark that block final, meaning it is considered settled. After that, a relayer or verification system passes the transfer information along, and a transaction must execute on the destination chain.
Those stages explain why seeing “confirmed” on the source chain does not always mean the tokens have arrived. Chainlink CCIP documentation describes the wait for source-chain finality before validation and destination execution; Circle CCTP documentation describes a USDC transfer using a source-chain burn, a signed attestation, and a destination-chain mint. An omnichain service can package routing and token conversion into one request, but the underlying route still determines the wait.
As a quick what-if, imagine swapping ETH on Ethereum for USDC on Base. Even if the swap quote appears immediately, the route may need to wait for its chosen source-chain security threshold before sending the destination transaction. The two chains’ processing times and the route’s design affect the estimate.
Use the transaction hash—the identifier for your submitted transaction—to follow the transfer. Check these steps in order:
If the source transaction is confirmed but the destination transfer is still pending, allow time for verification and execution. Don’t submit the swap again while the original transfer is processing; first check the route’s status and whether it reports a failure or a recovery action. An omnichain route can simplify the handoff, but it cannot make every chain settle at the same speed.
No. A route may feel quick when both chains settle rapidly and the destination transaction executes promptly, but source-chain finality and cross-chain verification add time. Treat any displayed estimate as route-specific, not a guarantee. Congestion, chain design, and the security threshold chosen for the transfer can all change the wait.
Some Layer 2 networks have more than one meaningful confirmation stage: a quick initial confirmation and a later settlement stage tied to the underlying Layer 1. A route may wait for the later stage for security. The exact delay varies by network and route, so check the current estimate for the specific pair of chains.
Usually, you cannot speed up the cross-chain verification stage yourself. If the source transaction is still unconfirmed, the source wallet may offer a way to replace it with a higher network fee, but that does not bypass the route’s later checks. Check the transaction and route status before taking action.