How to Track a Cross-Chain Swap That Hasn’t Arrived

A cross-chain swap is tracked by following its source-chain transaction, identifying the transfer record created by the route, and checking for settlement on the destination chain. A confirmed transaction on the source chain does not by itself show that the output token has arrived.

Separating those checkpoints helps identify whether a delay is in the initial transaction, the cross-chain transfer, or the destination swap.

Start with the transaction hash shown by the wallet or swap interface. Open it in an explorer for the source chain and check whether it is pending, reverted, or confirmed; a confirmed receipt means the source-chain call executed, while a failed receipt means the route did not complete as submitted. Record the source chain, destination chain, input amount, token, and recipient address, since the route may send the output to an address different from the sending wallet.

Then use the swap interface’s status page or the protocol’s tracker, if it provides one. Across’s documentation, for example, describes checking a deposit by its transaction hash or deposit ID and distinguishes pending, filled, expired, and refunded states. A “filled” status indicates that a relayer has made the destination-chain transfer; it is not interchangeable with confirmation of the source transaction. For a Quickswap-related pending case, see the quickswap pending-swap steps for the detail that guide covers.

What should I check on the source chain?

Check the transaction receipt and the route’s emitted events. A successful receipt confirms execution, but the events can provide the identifiers and parameters needed to match that execution to a bridge record. Compare the event’s recipient and destination chain with the route details displayed when the swap was submitted; a mismatch can explain why the expected wallet balance has not changed.

Keep the original hash even if the interface supplies a separate deposit, order, or transfer ID. Different systems index transfers by different identifiers, and the protocol tracker may need one that an ordinary block explorer does not show prominently. If the transaction is still pending on the source chain, the cross-chain leg generally cannot be treated as submitted yet.

How do I verify the destination transfer?

Once the route tracker reports a fill or execution, open the destination transaction on an explorer for the destination chain. Confirm that its receipt succeeded, then inspect the token transfer and recipient address. The wallet balance is a useful final check, but token decimals, a different output token, or a recipient mismatch can make the displayed balance alone inconclusive.

Routes that combine a bridge and a destination-chain swap may have more than one destination action. In that case, an initial transfer can arrive before the final token conversion completes. Follow the route’s own status record through its terminal state, then check the final token contract and amount rather than assuming the first destination event is the swap’s output.

What does a pending status mean?

“Pending” is specific to the system reporting it. Across’s tracking documentation defines it as a deposit submitted but not yet filled by a relayer; its other states distinguish a completed fill from an expired deposit or a refund. Other routes may use different labels, so read the status definition provided by that protocol rather than inferring settlement from the word alone.

• Source transaction pending: check its receipt again before tracing a bridge leg.
• Source confirmed, route pending: use the route’s tracker and its required transfer identifier.
• Destination transaction confirmed: verify the token transfer and recipient.
• Expired or refunded: follow the protocol’s stated recovery path and confirm the return transaction on the source chain.

For most users, the clearest evidence of completion is a successful destination receipt plus the expected token transfer to the intended recipient. Keep both chain transaction hashes and the route identifier until that check is complete; together, they show where the transfer stopped and what evidence supports its reported status.