Cross-Chain Bridge Explorer

WHAT IT DOES

The Cross-Chain Bridge Explorer is a read-only tool that helps you inspect and understand cross-chain bridge transactions. Enter a bridge contract address and a transaction hash on the source chain, and the app fetches the transaction and receipt, displays the transaction status, source chain, from/to addresses, token symbol and amount transferred, bridge fee, destination chain information, and destination transaction hash (where available). The tool also attempts to detect bridge-specific events and token transfer events from the transaction logs, providing a comprehensive overview of the bridge operation. This is useful for users tracking cross-chain asset movements, developers debugging bridge integrations, and auditors verifying bridge transaction details.

HOW TO USE

1. Select your source network from the dropdown or connect your wallet to use its RPC endpoint.

2. Enter the bridge contract address (the contract that handles the bridge logic on the source chain).

3. Enter the transaction hash on the source chain that initiated the bridge transfer.

4. Click "Explore bridge tx" to fetch and display the bridge transaction details.

5. Review the details: transaction status, source chain, from/to addresses, token symbol, amount, bridge fee, destination chain, destination transaction hash, block number, and log count.

6. Use the "Clear" button to reset all fields and start a new exploration.

ONE TECHNICAL SECTION

This tool works by fetching the transaction and receipt for the given hash using ethers v5's provider.getTransaction() and provider.getTransactionReceipt() methods. It then analyzes the receipt logs to detect and parse relevant events. The tool looks for Transfer events (ERC-20/ERC-721) to identify the token being transferred and the amount. It also attempts to detect bridge-specific events by examining the topics of the logs — bridge contracts typically emit events with specific signatures that can be identified. While this tool does not hardcode any bridge addresses or ABIs, it uses a heuristic to detect bridge activity. For the destination chain and transaction, the tool looks for events that contain cross-chain data, such as a destination chain ID or a destination transaction hash. In cases where the bridge uses off-chain relays, the destination transaction may not be immediately available, and the tool will display that accordingly. This approach allows the tool to work with many bridges that follow common patterns, without requiring per-bridge configuration.

WHAT IT CANNOT SEE

This tool cannot track bridges that do not emit standard events or use custom architectures — some bridges use off-chain relays or private mempools that are not visible on-chain. It cannot track cross-chain transactions that use off-chain relays or private bridges where the destination confirmation is not recorded on-chain. The tool is limited by RPC availability and event query limits on each chain; if the source chain's RPC does not provide full logs, some data may be missing. It cannot verify that a bridge transaction has been fully settled on the destination chain beyond the available event data — the tool can only show what is emitted on the source chain. It cannot track non-EVM chains or bridges, nor can it predict bridge

PLEASE NOTE

Sites and services change over time and this app may need updating to match.