Event Log Aggregation Across Multiple Contracts

WHAT IT DOES

This tool connects to your EVM wallet and aggregates event logs from multiple contract addresses on the same chain. It filters events by contract address, event signature, block range, and topic parameters, collecting logs from all specified contracts into a single unified view. The tool uses chunked RPC queries with automatic backoff and halving to handle provider rate limits, ensuring reliable log fetching even over large block ranges.

HOW TO USE

Connect your Web3 wallet using the Connect button. Enter the contract addresses you want to monitor—one per line in the Contract Addresses field. Optionally, enter an event signature (e.g., "Transfer(address,address,uint256)") to filter by specific event types. Specify the total block range to scan (default 10,000 blocks). Click "Fetch Logs" to begin aggregation. Click "Load Sample" to populate fields with example addresses. Results appear in the Results card with a summary of contracts scanned, total events found, and a detailed list of the most recent events with block numbers, contract addresses, topics, and data.

TECHNICAL MECHANISM: CHUNKED LOG FETCHING WITH RATE-LIMIT RESILIENCY

The tool uses ethers.js to fetch event logs from the RPC provider using eth_getLogs. To work around RPC block range limits (typically 10,000 blocks per request), the tool automatically divides the requested range into chunks of 2,000 blocks. If a chunk fails with a rate-limit error (code -32005 or message containing 'limit'), the tool halves the chunk size and retries, continuing until the request succeeds or the chunk size drops below 100 blocks. This progressive backoff ensures reliable log fetching across a wide variety of RPC endpoints, including public nodes with strict rate limits. The tool aggregates logs from all specified contracts, filtering by event signature when provided, and displays them in reverse chronological order.

WHAT IT CANNOT SEE

This tool cannot aggregate events across chains without separate RPC connections for each chain—it only works on the currently selected network. It cannot decode events without corresponding ABIs—logs are shown in raw format. It cannot guarantee that all events are captured due to RPC block range limits—very large ranges may still hit provider limitations. It relies on provider availability and may be rate-limited by RPC endpoints—fetching many logs may take time. It cannot detect events that are not emitted or are emitted in non-standard formats—the tool only reads standard event logs.

PLEASE NOTE

This is a read-only tool—it never signs transactions. All data is fetched on-demand and stored only in memory; nothing is persisted across page reloads. The tool supports EVM chains only—Ethereum, Polygon, BSC, Arbitrum, Optimism, Base, and their testnets. Event signatures must match the exact format used by the contract. The tool automatically handles RPC rate limits through chunking and backoff—large ranges may take time but will complete reliably.