Across Bridge Explorer
Free to download on every platform. Comes pre-installed on BotFone, BotPad and BotFlip — with extra free apps included.
About this app
WHAT IT DOES
The Across Bridge Explorer is a read-only tool that lets you inspect Across Protocol bridge transactions. Enter a source transaction hash and the Across 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, relayer fee, destination chain ID, fill status (pending, filled, or claimed), fill deadline, block number, and a count of Across events found. The tool analyzes transaction logs to detect Across's standard events — Deposit (when funds are deposited into the bridge), Fill (when a relayer fills the deposit), Claim (when the deposit is claimed on the destination), and Relay (when the deposit is relayed). This gives you a comprehensive view of your Across bridge transaction from deposit through to final settlement. This is useful for users tracking their bridge transfers, developers debugging cross-chain flows, and auditors verifying Across protocol 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 Across bridge deposit).
3. Enter the Across bridge contract address on the source chain.
4. Click "Explore bridge tx" to fetch and display the bridge transaction details.
5. Review the details: source status, source chain, from/to addresses, token symbol, amount, relayer fee, destination chain, fill status, fill deadline, block number, and count of Across events found.
6. Use the "Clear" button to reset all fields and start a new exploration.
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 Across-specific events. The tool looks for the Deposit event using its signature hash, which is emitted when a user deposits funds into the Across bridge. It also detects the Fill event, which is emitted when a relayer fills the deposit on the source chain, the Claim event, which is emitted when the deposit is claimed on the destination chain, and the Relay event, which is emitted when the deposit is relayed to the destination chain. For each event, the tool extracts relevant data such as amount, relayer fee, destination chain ID, fill deadline, and deposit ID. The tool also looks for Transfer events to identify the token being bridged. This event-based approach allows the tool to work with the standard Across interface across different EVM chains without requiring per-chain configuration.
WHAT IT CANNOT SEE
This tool cannot track Across bridge transactions that use private relays or off-chain settlement beyond on-chain events — some Across transactions may use custom relayers or off-chain execution that do not emit standard events. It cannot view deposits that have not been filled or claimed on-chain; if the deposit is still pending or executed off-chain, the tool will only show the Deposit event. 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, as Across only operates on EVM-compatible chains. It cannot predict fill times or final settlement delays, which depend on relayer activity and network conditions. It also cannot verify relayer integrity or bridge security without additional Across protocol data — the tool shows events but does not validate the relayer's reputation or the bridge's security guarantees.
PLEASE NOTE
This tool works only with EVM-compatible chains that support standard RPC methods and host the Across bridge contract. The fill status is based on event detection; for full confirmation, check the Across protocol interface or the destination chain directly. The tool is read-only and does not sign or send transactions. Always verify Across bridge transaction details with official Across interfaces and multiple sources before relying on this data for financial decisions.