Cross-Chain Transfer Tracker

WHAT IT DOES

The Cross-Chain Transfer Tracker is a read-only analytics tool that lets you track the status and details of cross-chain bridge transfers. Enter a source transaction hash and bridge contract address, and the app fetches the transaction and receipt, displays the transfer status, source chain, from/to addresses, token symbol and amount, bridge fee, destination chain information, and destination transaction hash (where available). The tool analyzes the transaction logs to detect Transfer events (for the token being bridged) and bridge-specific events, giving you a comprehensive view of the cross-chain transfer. This is useful for users monitoring their bridge transactions, developers debugging cross-chain flows, and auditors verifying bridge operations.

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 "Track transfer" to fetch and display the transfer details.

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

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

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 (standard ERC-20/ERC-721/ERC-1155) to identify the token being transferred and the amount. It uses the event signature hash of Transfer(address,address,uint256) to locate these events. 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 additional bridge metadata such as destination chain identifiers and fees from the logs. This event-based approach allows the tool to work across different bridges that follow common patterns, without requiring per-bridge configuration. The tool also uses the transaction receipt's status field to determine if the source chain transaction succeeded, which is a prerequisite for the bridge to process the transfer.

WHAT IT CANNOT SEE

This tool cannot track transfers that use non-standard bridge architectures or off-chain settlement — some bridges use custom event formats or settle transfers entirely off-chain, making them invisible to on-chain log analysis. It cannot verify final settlement on destination chains beyond the available event data; if the destination transaction is not emitted as an event or is settled off-chain, the tool will show it as unavailable. The tool is limited by RPC availability and event query limits — 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 cross-chain transfer completion times or fees — these are determined by the bridge operator and network conditions. The tool cannot detect failed transfers that do not emit failure events — some bridges may fail silently without emitting error logs.

PLEASE NOTE

This