Bridge Transaction Viewer

WHAT IT DOES

The Bridge Transaction Viewer is a read-only tool that provides a complete view of cross-chain bridge transactions. Enter a source transaction hash and bridge contract address, and the app fetches the transaction and receipt from the source chain. It then displays the source transaction status, from/to addresses, token symbol and amount, bridge fee, destination chain information, destination transaction hash (if available), and destination status. The tool analyzes transaction logs to detect Transfer events and bridge-specific events, giving you a comprehensive picture of the bridge operation from start to finish. This is useful for users tracking their bridge transfers, developers debugging cross-chain flows, and auditors verifying bridge transactions.

HOW TO USE

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

2. Enter the source transaction hash (the transaction on the source chain that initiated the bridge transfer).

3. Enter the bridge contract address on the source chain.

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

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

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

ONE TECHNICAL SECTION

This tool uses ethers v5's provider.getTransaction() and provider.getTransactionReceipt() methods to fetch the source transaction and its receipt. It then analyzes the receipt logs to detect relevant events. The tool looks for Transfer events using the standard Transfer(address,address,uint256) signature hash, which identifies the token being bridged and the amount. For bridge-specific events, the tool examines all log topics and counts events with 32-byte topic hashes, which are typically emitted by bridge contracts. The tool also attempts to extract destination information from the logs — many bridges emit events containing the destination chain ID and the recipient address. The tool displays the source transaction status from the receipt status field, and provides a heuristic destination status based on whether destination events are found. This event-based approach allows the tool to work across different bridges that follow common patterns, without requiring per-bridge configuration.

WHAT IT CANNOT SEE

This tool cannot track bridges that use off-chain settlement or private relays — if the bridge does not emit on-chain events for the destination settlement, the tool cannot show it. It cannot view bridge transactions that are not fully settled on-chain; some bridges use off-chain relays that only submit batch settlements, making individual transactions invisible. 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 track non-EVM chains or bridges that operate on non-EVM networks. It cannot predict bridge processing times or final settlement delays — these depend on the bridge operator and network conditions. It also cannot verify that the destination transaction matches the source without cross-referencing bridge-specific event data, which may not be available for all bridges.

PLEASE NOTE

This tool works only with EVM-compatible chains that support standard RPC methods. The bridge detection is event-based and may not work with all bridges, especially those that