Why pending is the default here
A same-chain swap finishes when one network confirms it. A cross-chain swap cannot, because two networks that never talk to each other are involved. The route has to be settled on the source, carried across by a bridge or liquidity network, and then settled again on the destination. Each of those is a real step with its own wait.
So pending on a cross-chain swap is not a warning. It is the status that covers the whole journey, including the gaps between legs where the value is committed but not yet visible on either side. The useful question is not whether it is pending but which leg it is currently on.
The legs of the route
A typical cross-chain swap breaks into three legs. Tracing them tells you where your funds are right now.
Source confirmation
Your input transaction has to be included on the source chain and reach the confirmation depth the route requires. Fast chains clear this in seconds to a couple of minutes. Bitcoin and other slower chains take much longer, and some routes deliberately wait for several blocks before proceeding.
Nothing on the destination can start until this depth is reached. If this leg is slow, everything downstream waits with it.
The bridge or liquidity step
Once the source is deep enough, the route moves the value across. Depending on the path this is a bridge locking and releasing, or a liquidity network or solver filling the destination from its own reserves and reconciling later. A filled route can feel almost instant. A route that waits for full bridge settlement is slower.
This middle leg is where much of the variation lives, and it is often not visible on a plain block explorer. A routing engine's own status page is the place to see it.
Destination settlement
The output transaction is submitted on the destination chain and has to confirm there. It depends on that chain's speed and congestion at the moment. When this confirms, the swap is done and the received asset is spendable, provided your wallet lists the token and is set to that network.
What governs the timing
The realistic window is set by the slowest chain in the route, not by an average. A few factors dominate.
- Source confirmations, which are fast on high-throughput chains and slow on Bitcoin.
- Required confirmation depth, since some routes wait for several blocks before releasing.
- The route type, where a liquidity fill is quicker than waiting on full bridge settlement.
- Destination speed and congestion, which apply to the final leg.
- Network load on either side, which stretches every step under demand.
When to wait and when to seek help
Between two fast chains, a cross-chain swap can complete in minutes. Involving Bitcoin, allow considerably longer for its confirmations. The honest expectation is a range set by the slowest network in the route, not a fixed number, so give the route the time its legs need before treating it as a problem.
If the source confirmed but the destination has not arrived well past the typical window for those networks, check the transaction hash on the routing engine's status page if one is available, then contact support with the hash. Do not resend, since a duplicate attempt can complicate tracing and recovery of the first.