0
0

Delete article

Deleted articles cannot be recovered.

Draft of this article would be also deleted.

Are you sure you want to delete this article?

Cross-Chain Swap Tracking for Beginners

0
Posted at

Cross-chain swap tracking means following one transfer on both the sending and receiving blockchains. The key is that a successful source transaction does not prove the destination transfer has finished. A block explorer is a website that shows a chain’s recorded transactions.

  • Start with the source transaction hash and the correct source-chain explorer.
  • Check whether the source transaction succeeded before investigating the destination.
  • A completed source step can still be waiting for a separate destination step.

Start with the source transaction

Find the transaction hash in your wallet’s activity or the swap service’s receipt. A hash is the transaction’s unique reference, often a long string beginning with “0x” on EVM chains. Search for it on the explorer for the chain you sent from; the same hash format can appear on different chains.

Read the status and the details together. “Pending” means the chain has not yet included the transaction in a block. “Success” means the source-chain action ran, while “Fail” or “Reverted” means it did not complete. Ethereum.org explains that transactions move from a pending pool into a block, then gain more certainty as the block is confirmed and finalized.

For example, imagine swapping 100 USDT from Base to Arbitrum. If the Base explorer says “Pending,” the bridge has no confirmed source action to process yet. If it says “Success,” inspect the token transfer and contract interaction to check that the expected token left your wallet and the route contract received it.

For how fermi swap routes a transfer, see the full step-by-step explanation of the route, costs, and common delays. This article focuses on reading the evidence when your own transfer appears stuck.

Follow the transfer to the destination

A bridge transfer usually has more than one on-chain step: the source chain records your deposit or swap, then bridge operators or contracts arrange execution on the destination. The destination transaction may have a different hash, so searching the source hash on the destination explorer often finds nothing. Look in the swap service’s activity or status view for a destination link, or use its support instructions to find the message or transfer reference.

Check that the destination link names the intended chain and wallet. Then look for a successful transaction and a token credit to the destination address. For USDT, check the token’s transfer record as well as the wallet balance; the balance display may update late, or the wallet may not yet show that token.

Axelar’s documentation describes this gap clearly: a source-chain call is followed by validation and a separate destination execution. That means the useful question is not only “Did my send succeed?” but also “Has the destination action been submitted and completed?” A bridge tracker may show stages such as confirming, processing, or delivered, but labels vary by route.

Use the status to choose your next step

  • Source pending: Wait for inclusion, then refresh the source explorer. On Ethereum, a low fee can leave a transaction waiting longer when the network is busy.
  • Source failed: The swap did not complete on that chain. Check the failure reason and wallet balance; the network may still charge a fee for the failed attempt.
  • Source succeeded, destination missing: Find the bridge status or destination reference. If it remains unfinished beyond the service’s stated time, contact its support with both chain names, the source hash, and the destination address.
  • Destination succeeded, balance missing: Confirm the recipient address and token contract, then refresh or add the token in your wallet.

These are two different cases: a failed source transaction usually calls for fixing the cause before trying again; a successful source transaction with no destination result calls for tracing the existing transfer first. Sending again can create a second swap and another fee. With fermi swap, follow the receipt’s route-specific status before deciding that a retry is needed.

Explorers are free to read, but a replacement transaction or another swap can cost network fees; the amount depends on chain activity and the action. Never share a recovery phrase or approve a stranger’s “unlock” transaction. For support, provide public transaction details only, and verify the support channel through the service’s official site.

Takeaway: confirm the source, trace the destination step, and retry only after you know where the first transfer stopped.

0
0
0

Register as a new user and use Qiita more conveniently

  1. You get articles that match your needs
  2. You can efficiently read back useful information
  3. You can use dark theme
What you can do with signing up
0
0

Delete article

Deleted articles cannot be recovered.

Draft of this article would be also deleted.

Are you sure you want to delete this article?