How to track a cross-chain swap that is taking too long
A source transaction does not prove a cross-chain swap arrived. Check its hash, bridge status, destination receipt and refund deadline before retrying.
BitCurrent Newsroom2 min read
A cross-chain swap is tracked in two stages: confirm the source transaction, then verify the destination delivery or refund. A successful source transaction proves the deposit was accepted, not that the output has arrived.
- 10 seconds: one bridge’s status indexer checks for updates at this interval.
- 1–15 seconds: its documented range for indexer delay after a deposit.
- Four possible outcomes: pending, filled, expired or refunded.
Why does my swap look stuck?
First check the source-chain hash in that chain’s block explorer. A pending transaction has not yet been included in a block; a failed one did not make the deposit.
If it succeeded, the bridge may still be processing the transfer or its tracker may not have caught up. For route mechanics, see QuickSwap Ethereum-to-Solana routing. That routing detail is separate from the status of your own transfer.
Which transaction should I follow next?
Use the bridge’s status page or tracker with the source transaction hash. Some bridges also identify a deposit by its origin chain and deposit ID, which may appear in the transaction’s emitted events.
Read the status carefully. “Pending” means the deposit is recorded but the destination leg is not marked complete; “filled” means the bridge reports delivery. Open the destination transaction hash, if provided, in the destination chain’s explorer and check its result and recipient.
A tracker can lag behind the chain. One bridge documents a 1–15 second indexing delay, so a brief gap between source confirmation and a status update does not by itself show a failure.
What should I do if the destination is still empty?
Check that you are looking at the destination chain and the expected recipient address. Confirm the output token too; a swap may deliver a different asset from the one sent.
If the bridge still reports “pending,” use its stated fill deadline or support process to decide when to escalate. If it reports “expired,” check the bridge’s refund instructions and verify any refund transaction on the source chain. Do not send the swap again while the first deposit remains unresolved.
The useful distinction is simple: the source hash confirms the first leg, while a destination receipt or refund transaction confirms how the transfer ended.