Latency Profiler for Cross-Chain Calls

WHAT IT DOES

Latency Profiler for Cross-Chain Calls measures the time it takes for a call to propagate from one EVM chain to another. You provide transaction hashes from both the source and destination chains, along with their respective RPC URLs. The tool fetches the transaction receipts and block timestamps for each transaction, then calculates key latency metrics: source confirmation time, cross-chain latency (time from source block to destination block), destination confirmation time, and total end-to-end latency. Results are displayed with a summary dashboard and detailed timing breakdown. This is essential for developers debugging cross-chain bridges, measuring protocol performance, or optimizing cross-chain application latency.

HOW TO USE

Enter the source and destination chain names for context. Enter the source transaction hash and destination transaction hash. Enter the RPC URLs for both chains. Click "Profile Latency." The tool fetches the transaction receipts and block details from both chains using the provided RPC endpoints. It extracts block timestamps and calculates the time differences between the transactions. Results are displayed as a summary with cross-chain latency, source confirmation time, destination confirmation time, and total latency. Detailed information includes block numbers, timestamps, and a formatted time breakdown. Use this data to understand the end-to-end latency of your cross-chain calls.

THE REAL MECHANISM

The tool uses ethers.js v5.7.2's JsonRpcProvider to connect to both chain RPC endpoints. It fetches the transaction receipt for each transaction hash using provider.getTransactionReceipt. It then fetches the block for each receipt's block number using provider.getBlock to get the block timestamp. The tool calculates: source confirmation time (time from source block to source receipt), cross-chain latency (difference between source and destination block timestamps), destination confirmation time (time from destination block to destination receipt), and total latency (difference between source block timestamp and destination receipt time). Timestamps are in milliseconds for accurate comparison. All processing is done client-side—no data is sent to external servers beyond the RPC requests themselves.

WHAT IT CANNOT SEE

This tool cannot measure latency without user-provided transaction hashes—you must have both hashes. It cannot profile non-EVM chains. It cannot distinguish between network latency and block time latency—it measures total time including block times. It cannot measure cross-chain message delivery latency that involves off-chain relayers or bridges that don't produce on-chain transactions on both sides. It cannot simulate cross-chain calls or predict future latency. It cannot measure latency for chains that do not provide accurate block timestamps—some chains may have unreliable or unavailable timestamps. The tool does not account for transaction submission time—it measures from block inclusion.

PLEASE NOTE

Latency Profiler works exclusively with EVM-compatible chains that support eth_getTransactionReceipt and eth_getBlock. It requires valid RPC URLs and transaction hashes that have been confirmed on both chains. The tool reads data only and does not send any transactions. All processing occurs client-side in your browser; no data is sent to any external server. The tool is free to use and does not require authentication. For accurate measurements, ensure both transactions are from the same cross-chain call flow.