How to Trace a Cross-Chain Bridge Transaction Using Two Explorers

04 October 2026

You can trace a cross-chain bridge transaction by following the transaction hash from the source chain to the bridge contract, then locating the corresponding mint or release event on the destination chain using a second explorer. The process is mechanical, though it varies slightly depending on whether the bridge uses lock-and-mint, burn-and-mint, or a liquidity pool model. The key is to stop looking for a single transaction that spans both chains - no such record exists. Instead, you are looking for two linked transactions, connected by the bridge’s internal logic.

What you are actually looking for

A cross-chain bridge does not move tokens. It locks or burns tokens on the source chain, then instructs the destination chain to mint or release an equivalent amount. The bridge operator, or a validator set, watches the source chain for deposit events, then signs a message that triggers the destination chain transaction. Your job is to find that destination transaction using the source transaction’s hash and a block explorer for each chain.

The source transaction is the one you submitted. The destination transaction is the one the bridge submitted on your behalf. They are not the same hash. They are not even on the same network. You will need one explorer for the chain you sent from, and one for the chain you sent to.

Step 1: Confirm the Source Transaction on the Origin Explorer

Start with the transaction hash you already have. Paste it into the origin chain’s explorer - Etherscan for Ethereum, BscScan for BNB Smart Chain, PolygonScan for Polygon, and so on. You should see a normal transaction record with a status, block number, timestamp, and fee.

Look for the “To” field. That address is the bridge contract. Write it down. Also note the “From” field - that is your wallet address. The “Value” field shows the amount of the native asset sent, but if you bridged a token, you will need to click the “Logs” or “Events” tab to see the token transfer.

Open the “Logs” tab. You are looking for a Deposit, Lock, or Transfer event. The bridge contract emits a specific event when it receives your funds. That event contains the details the bridge validators will later use. The event will include:

• The sender (your address)
• The token address
• The amount
• A destination address (often your address on the other chain, but sometimes a relayer-supplied address)
• A nonce or ID that uniquely identifies this deposit

Copy the transaction hash and the relevant event data. You will not need all of it, but you will need the token address and the destination address.

Step 2: Identify the Bridge Type and Find the Destination Contract

Now you need to know how the bridge works. Not all bridges are the same, and the explorer steps differ.

• Lock-and-mint bridges (Wrapped Bitcoin, Wrapped Ether on some chains): Your tokens are locked in a contract on the source chain. The bridge mints a wrapped version on the destination chain. You will look for a Mint event on the destination.
• Burn-and-mint bridges: Your tokens are burned on the source chain. The bridge mints the original token on the destination chain. You will look for a Mint event.
• Liquidity pool bridges (many newer bridges): Your tokens are swapped into the bridge’s pool on the source chain. The bridge pays out from a pool on the destination chain. You will look for a Transfer or Swap event on the destination.

In all cases, the bridge contract on the source chain has a counterpart on the destination chain. The destination contract address is usually listed on the bridge’s official documentation or on the source transaction’s decoded event. Some explorers show a “Bridge” tab that attempts to link the two transactions automatically. If it works, use it. If not, proceed manually.

Step 3: Search the Destination Explorer by the Bridge’s Destination Contract

Open the destination explorer. For example, if you bridged from Ethereum to Arbitrum, open Arbiscan. Paste the destination bridge contract address into the search bar. This shows you all transactions involving that contract.

You cannot search directly for your destination transaction by your source hash. Instead, you need to find the transaction where the bridge emitted the Mint or Transfer event that credits your destination address.

If you have the destination address (from the source event), you can filter the destination contract’s transaction list by that address. Many explorers let you click on the contract address, then go to the “Transactions” or “Internal Transactions” tab, and use the search box to filter by your wallet address.

Step 4: Match the Deposit Nonce or Amount

Once you find a candidate transaction, open it. Check the “Logs” tab. You are looking for a Mint or Transfer event where:

• The recipient is your destination address
• The amount matches the source amount minus any bridge fee
• The token address matches the expected token

The bridge may also include a depositNonce or depositID in the logs. If you have that value from the source event, match it exactly. If the amounts are rounded or reduced by fees, the nonce is the more reliable match.

Step 5: Verify the Destination Transaction Is Final

Do not stop at finding the transaction. Check the block number and the number of confirmations. On the destination chain, the transaction must have enough confirmations to be considered final - usually the same confirmation count you would trust for any regular transaction on that chain. If the destination transaction is still pending or was replaced, you have found the wrong one.

What Can Go Wrong and How to Read the Signs

• No matching destination transaction yet. Bridges can take minutes to hours. Check the bridge’s status page for delays.
• The destination transaction was reverted. The logs will show a failed transaction. This usually means the bridge tried to mint but hit an error - for example, a paused contract or a token blacklist. You may need to contact the bridge support.
• The bridge uses a relayer and the relayer failed. The destination transaction may not exist. You will see the source deposit confirmed, but no destination activity. This is a bridge operational issue, not something your explorer can fix.
• You sent to a bridge that uses a different model than you assumed. If you cannot find a mint event, check whether the bridge uses a liquidity pool. The destination transaction may be a normal transfer from the pool contract, not a mint.

A Practical Example

Suppose you sent USDC from Ethereum to Polygon via the official Polygon bridge. On Etherscan, your source transaction shows a Deposit event from your address to the Polygon bridge contract. The event includes a destinationChainId and a depositNonce. You copy the deposit nonce.

Open PolygonScan. Go to the Polygon bridge contract address (listed on Polygon’s docs). Look at its recent transactions, filter by your destination wallet address, and find the transaction that includes a Mint event with the same deposit nonce. Open the logs, confirm the recipient and amount, and you are done.

When you cannot find it

If you have followed these steps and there is no destination transaction, the bridge is either slow, failed, or the transaction was never submitted. Do not assume you lost your funds. Check the bridge’s official status page and transaction history. If the bridge is decentralized, check the validator set’s recent activity. If the bridge is custodial, contact their support with both the source transaction hash and the deposit nonce.

The two-explorer method is the only reliable way to trace a cross-chain move. It is tedious the first time, but after two or three attempts it becomes a routine two-minute check.

Back to block explorers