Track Both Legs of a Cross-Chain Swap to Your Wallet

To track a cross-chain swap to your wallet, follow its source-chain transaction until the bridge or route completes on the destination chain. A wallet signature starts the process; it does not prove that the destination token has arrived. Save the transaction hash shown after signing, and note the source and destination networks, token, amount, and receiving address.

A cross-chain route may swap tokens before or after bridging, or use a bridge that delivers the destination asset directly. The tracker for fermi swap is one place to see how a route’s steps fit together. The key distinction is that the source transaction and destination delivery are separate onchain events, even when one interface presents them as a single transfer.

Which transaction hash should you use?

Start with the source transaction hash, the unique identifier for the transaction submitted to the sending chain. Open it in an explorer that supports that network and check whether it was included and succeeded. A pending transaction has not yet been confirmed; a failed transaction did not complete its onchain action. Neither status alone tells you whether a separate destination transaction has finished.

Next, open the swap or bridge interface’s activity page, if it provides one. Paste the source hash or open the recorded transfer. Look for a route status and a destination transaction hash. The source explorer records what happened on the sending chain; the route tracker connects that event to the later delivery. If the interface shows only a transaction ID, use its own status page to resolve it rather than searching that ID as though it were necessarily an explorer hash.

How do you confirm the tokens reached your wallet?

Check the destination transaction on an explorer for the receiving network. Confirm that it succeeded, then verify the recipient address and token contract in the transaction details or token transfer events. A familiar token ticker is not enough: different contracts can use the same symbol, and a wallet may not display a token automatically.

Compare the amount received with the route’s estimate and minimum amount. A difference can reflect the quoted fees, a destination swap, or price movement within the route’s slippage limit. The destination token may also differ from the source token if the route included a swap. Add the token by its verified contract address if the transfer succeeded but the balance is not visible in the wallet.

What does a delayed or failed status mean?

A successful source transaction means the source chain accepted the transfer instruction; the route may still need to relay a message, wait for confirmation, or execute a destination transaction. The tracker’s latest stage helps identify where it stopped. A missing destination hash can mean the destination step has not yet been submitted, while a failed destination transaction means delivery needs a separate recovery path.

• Source pending: Check the source chain and transaction status before taking another action.
• Source failed: Confirm whether the tokens remain in the sending wallet and review the failure details.
• Route pending: Keep the source hash and route record; check the route interface for its stated next step.
• Destination succeeded: Verify the recipient, token contract, and transfer amount on the receiving chain.

Use the original route interface’s recovery instructions when a route reports a failure, and verify the site address before connecting a wallet. Do not submit the same transfer again just because the destination balance is not yet visible. For most users, the reliable check is the destination transaction and recipient balance, with the route tracker explaining the time between the two chain events.