Rollup Transaction Aggregator

WHAT IT DOES

This tool aggregates and displays rollup transaction batch data from Layer 2 networks. It reads sequencer batch submissions, transaction groupings, state roots, and batch hashes directly from L2 batch contracts. Instead of relying on block explorers or third-party dashboards, you connect directly to the blockchain via your wallet's RPC provider and retrieve raw rollup data. You can inspect batch submission events, read batch counters and state roots, and correlate L2 blocks with their corresponding batch information. The tool is designed for rollup developers, auditors, and researchers who need to understand how transactions are batched and submitted to L1.

HOW TO USE

Connect your wallet using the BGWallet bridge and select your target rollup network (Optimism, Arbitrum, Base, zkSync, Linea, or others). Choose the aggregation type: Transaction batches, Sequencer contract state, Block with L2 batch info, or Transaction & L1 batch info. For batch aggregation, enter the sequencer contract address and the number of recent batches to fetch. For contract state, enter the L2 batch contract address to read batch counters, state roots, and sequencer/owner addresses. For blocks, enter a block number to see its state root and transaction count. For transactions, enter a transaction hash to see its block and batch context. Click "Aggregate rollup data" to execute the query.

TECHNICAL MECHANISM

The tool uses ethers.js v5.7.2 to interact with the blockchain via BGWallet's provider. For batch aggregation, it fetches logs using eth_getLogs with automatic chunking and halving on limit errors, searching for BatchSubmitted, BatchAppended, and SequencerBatchAppended events. It reads batch counters using batchCount() or totalBatches() and can retrieve individual batch hashes using getBatch(). For contract state, it calls common L2 batch contract methods (totalBatches, sequencer, owner, latestStateRoot, stateRoots) to read the current state. For blocks and transactions, it retrieves block headers with stateRoot and transaction receipts. All BigNumber values are converted to strings for readable output.

WHAT IT CANNOT SEE

This tool cannot verify that the batch data is valid or correctly sequenced. It cannot detect sequencer omissions, reordering, or censorship. It cannot verify the correctness of state transitions or validate that the state roots correspond to the actual L2 state. It cannot detect fraud or invalid state roots without additional verification logic (e.g., executing the transactions yourself). It cannot prove that the L2 state root matches the L1 commitment without L1 access. It cannot read batch data that is not submitted on-chain or is submitted in a non-standard format. You are responsible for understanding the rollup's security model and verifying its trust assumptions.

PLEASE NOTE

EVM chains only. Supports Optimism, Arbitrum, Base, zkSync, Linea, and other EVM rollups with standard batch submission contracts. Does not support Solana, Tron, Starknet (non-EVM), SUI, TON, Aptos, Bitcoin, Cosmos, or XRP. Requires a wallet connected via BGWallet to provide the RPC provider. The tool is read-only and does not sign any transactions. Always verify the contract address and batch data independently before relying on the results.