Detailed Instructions

Before you can track your transaction, you must first gather the source transaction hash (TxID) and the source chain identifier. These are your primary keys for any cross-chain explorer. The transaction hash is a unique string of letters and numbers generated when you initiate the transfer on the originating blockchain (e.g., Ethereum, BNB Smart Chain).

• Sub-step 1: Locate the transaction hash in your wallet's transaction history or from the block explorer of the chain you sent from. For example, an Ethereum hash looks like 0x4a7b8c9d1e2f3a4b5c6d7e8f9a0b1c2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9.
• Sub-step 2: Identify the source chain name and chain ID. Common chain IDs are 1 for Ethereum Mainnet, 56 for BSC, and 137 for Polygon.
• Sub-step 3: Note the exact token amount, recipient address on the destination chain, and the bridge/dApp name you used (e.g., Multichain, Stargate, Wormhole). This information is crucial for filtering results.

Tip: Bookmark the block explorer for your source chain (like Etherscan for Ethereum) for quick access to transaction details.

Detailed Instructions

Dedicated cross-chain explorers like LayerZero Scan, Axelarscan, or the specific explorer for your bridge (e.g., Wormhole Explorer) are designed to track messages and assets across networks. These tools map the source transaction to corresponding events on intermediary and destination chains.

• Sub-step 1: Navigate to a cross-chain explorer's website. For a LayerZero-based transfer, you would go to scan.layerzero.network.
• Sub-step 2: Paste your source transaction hash into the search bar and select the correct source chain from the dropdown menu.
• Sub-step 3: Review the explorer's output. It should display a detailed timeline showing: the source chain send event, the cross-chain message hash, the relayer/validator confirmation, and the final destination chain receive event. Look for statuses like Delivered or Execution Successful.

Tip: If the primary explorer shows delays, check the status of the underlying cross-chain messaging protocol (e.g., LayerZero, CCIP) for any known network congestion or issues.

Detailed Instructions

Even after a cross-chain explorer shows success, you must independently verify the funds have arrived in the destination wallet. This involves checking the native block explorer for the destination chain (e.g., Polygonscan for Polygon, Arbiscan for Arbitrum).

• Sub-step 1: Take the destination transaction hash provided by the cross-chain explorer or locate your wallet address on the destination chain's block explorer.
• Sub-step 2: On the destination explorer, search for your wallet address. Filter transactions to show only incoming (IN) transfers.
• Sub-step 3: Identify the transaction that matches the token amount and approximate time. Confirm its status is Success. Verify the contract address of the received token matches the expected canonical token address for that chain. For example, the canonical USDC address on Arbitrum One is 0xaf88d065e77c8cC2239327C5EDb3A432268e5831.

codeCopy
// Example: Checking wallet balance via RPC
const Web3 = require('web3');
const web3 = new Web3('ARBITRUM_RPC_URL');
const tokenContract = new web3.eth.Contract(ERC20_ABI, '0xaf88d065e77c8cC2239327C5EDb3A432268e5831');
const balance = await tokenContract.methods.balanceOf('YOUR_WALLET_ADDRESS').call();
console.log('USDC Balance:', balance / 1e6);

Tip: Always add the destination chain's native token (e.g., MATIC for Polygon) to your wallet to pay for gas fees to move or swap the bridged assets.

Detailed Instructions

If your transaction is stuck in a pending state or the cross-chain explorer shows an error, systematic troubleshooting is required. Common issues include insufficient destination gas, validator/relayer delays, or bridge contract congestion.

• Sub-step 1: Check Bridge Status Pages. Visit the official status page or Twitter/X account of the bridge service (e.g., Multichain, Synapse) for announcements about outages or slow finality.
• Sub-step 2: Verify Gas on Destination. Ensure the receiving wallet has a small amount of the destination chain's native gas token. Some bridges require it for automatic claiming; if not, you may need to manually execute a claim function.
• Sub-step 3: Use Transaction Foraging Tools. For certain bridges like Hop or Across, you can use their official UIs to "force" or "replay" a transaction by inputting your source hash.
• Sub-step 4: Review Smart Contract Events. On the source chain explorer, find your transaction and examine the internal transactions and event logs. Look for a specific cross-chain transfer event (e.g., BridgeInitiated). The absence of this event means the bridge interaction failed on the source side.

Tip: For long delays (over 24 hours), gather your source TxID, destination address, and bridge name, and contact the bridge's official support channel. Never share your private key.

Detailed Instructions

Every blockchain transaction is assigned a unique transaction hash (TXID). This is your primary tracking number. If your transaction appears to have failed or is stuck, the first step is to retrieve this hash from the wallet or dApp interface you used to initiate the transfer.

• Sub-step 1: Open the wallet history or activity tab in the application you used (e.g., MetaMask, Phantom). Locate the specific cross-chain transfer attempt.
• Sub-step 2: Click on the transaction to view its details. The TXID is typically a long alphanumeric string (e.g., 0x4a7f8a9c1b2d3e4f5a6b7c8d9e0f1a2b3c4d5e6f7a8b9c0d1e2f3a4b5c6d7e8f9). Copy it to your clipboard.
• Sub-step 3: If the wallet doesn't show it, check your email for a confirmation receipt from the bridge or dApp service, which often includes the TXID.

Tip: Always double-check you are copying the full hash. Missing even one character will make tracking impossible.

Detailed Instructions

Navigate to the block explorer for the source chain (e.g., Etherscan for Ethereum, Solscan for Solana). Paste your TXID into the search bar. The explorer provides a detailed receipt of the transaction's lifecycle.

• Sub-step 1: Confirm the transaction status. Look for labels like Success, Failed, Pending, or Dropped. A Success status here means the funds left your wallet on the source chain.
• Sub-step 2: Examine the "To" address and input data. Verify the transaction was sent to the correct bridge or router contract. For example, a common Wormhole bridge contract on Ethereum is 0x3ee18B2214AFF97000D974cf647E7C347E8fa585.
• Sub-step 3: Review gas fees and events. Check if the gas (Gas Used) was sufficient. Look in the Logs or Events section for specific bridge events like TransferRedeemed or LogMessagePublished, which confirm the bridge processed the request.

Tip: A Failed status on the source chain often means the transaction was reverted due to low gas, a price slippage error, or insufficient liquidity. The funds never left your wallet.

Detailed Instructions

Cross-chain bridges and relayers have their own tracking systems. You need to find the destination chain transaction hash.

• Sub-step 1: Go to the official website of the bridge you used (e.g., Portal Bridge, Axelar, LayerZero). Find their transaction tracker or "txn status" page.
• Sub-step 2: Input your source TXID. The bridge dashboard should show the relay progress and, crucially, provide the new transaction hash for the destination chain. If it shows "Pending," the relayer may be waiting for more confirmations.
• Sub-step 3: If no dashboard exists, manually check the destination chain's explorer. You may need to look for a specific transaction triggered by the bridge's relayer address. Search for transactions to your destination wallet address that occurred shortly after the source transaction.

Tip: Some bridges require you to manually claim funds on the destination chain. The dashboard will provide a claim transaction button or a specific claim function call data.

Detailed Instructions

The final step is to confirm asset arrival on the destination chain. Use the destination chain's block explorer (e.g., Arbiscan for Arbitrum, Snowtrace for Avalanche) with the hash provided by the bridge.

• Sub-step 1: Verify transaction success. On the destination chain explorer, ensure the transaction status is Success. This confirms the assets were minted or transferred to your address on this chain.
• Sub-step 2: Check token contract addresses. Cross-chain assets are often wrapped tokens. Verify the received token's contract address matches the official canonical address for that asset on the new chain. For example, USDC on Arbitrum is 0xFF970A61A04b1cA14834A43f5dE4533eBDDB5CC8.
• Sub-step 3: If the transaction failed here, decode the error. In the explorer, look at the transaction input data. You might need to decode it to see a revert reason. Common command-line tools can help:

bashCopy
cast receipt <TXID> --rpc-url <RPC_ENDPOINT> | jq .logs

Tip: Persistent failures often require contacting the bridge's support with all collected TXIDs. Timeouts can occur if a relayer is offline; sometimes re-submitting the claim or waiting longer is the solution.