How to Read a Rollup Transaction on a Block Explorer

08 October 2026

The short answer: you read a rollup transaction on a block explorer by understanding that most of what you see is a batch of compressed data posted to the L1 chain, not a line-by-line record of individual user actions. L2 block explorers decode this data for you, but knowing what sits behind the numbers helps you avoid confusion about fees, finality, and which chain actually processed your transaction.

What a rollup transaction actually is

On Ethereum mainnet, a transaction is a direct state change: you sign a message, it gets included in a block, and the block explorer shows you the sender, receiver, value, and gas used in a straightforward format.

On a rollup, the transaction you submit to the L2 sequencer is not individually stored on L1. Instead, the sequencer compresses thousands of L2 transactions into a single piece of data - usually a compressed calldata blob or a state diff - and posts that batch to the L1 chain as one L1 transaction. The block explorer for the rollup reads that batch and reconstructs the individual L2 transactions for display.

This means when you look up your L2 transaction on an L2 block explorer (like Arbiscan for Arbitrum or Optimistic Etherscan for Optimism), you are looking at a reconstructed view. When you look at the L1 block explorer (like Etherscan) for the same batch, you see only the compressed data.

Steps to Read an L2 Transaction on an L2 Block Explorer

1. find your transaction hash

You get this from the wallet or dApp that initiated the transaction. Paste it into the search bar of the rollup's official block explorer.

2. Identify the Basic Fields

Every L2 transaction shows:

• Status: Success, Pending, or Failed. Pending means the sequencer has accepted it but not yet included it in an L2 block.
• Block Number: The L2 block number, not the L1 block number. L2 blocks are far more frequent - often every few seconds.
• Timestamp: When the sequencer included the transaction. This is not the same as the L1 batch timestamp.
• From / To: Standard addresses. These are the L2 addresses, which are usually the same as your L1 address on EVM-compatible rollups.
• Value: The amount of ETH or token transferred. This is the L2-native balance, not an L1 balance.

3. Check the Fee Breakdown

Rollup fees differ from L1 fees. Look for:

• L2 Execution Fee: The fee paid to the sequencer for processing your transaction on the L2. This is typically very low (cents).
• L1 Data Fee: The fee for posting your transaction's data to L1. This varies with L1 gas price and the size of your transaction data. On Optimistic Rollups, this fee is often the larger component.
• Total Fee: The sum of both. If you see a surprisingly high fee, check whether L1 gas was spiking at that moment.

Some explorers show a "Gas Used" field, but this refers to L2 gas, not L1 gas. The L1 gas cost is calculated separately by the sequencer and shown as the L1 data fee.

4. Locate the Batch and L1 Transaction Link

Scroll down to a section usually labeled "Batch" or "L1 State Batch". This shows:

• Batch Number: The sequential batch your transaction was included in.
• L1 Transaction Hash: The actual L1 transaction that contains the compressed batch. Click this to see the raw calldata on Etherscan.

If you click the L1 transaction hash, you will see a regular L1 transaction with a "To" address that is the rollup's contract (the Inbox or CanonicalTransactionChain). The "Input Data" field contains hex-encoded compressed data. An L2 block explorer decodes this - you do not need to parse it manually.

5. understand finality status

Rollup explorers often show a "Finality" or "Confirmation" status:

• Sequenced: The sequencer has included it in an L2 block. This is fast (seconds) but not final.
• Submitted to L1: The batch containing your transaction has been posted to L1. On optimistic rollups, this triggers the challenge period (typically 7 days for Optimism, less for Arbitrum).
• Finalized: The challenge period has passed (on optimistic rollups) or the validity proof has been verified (on ZK rollups). After this, the transaction has the same security as an L1 transaction.

ZK rollup explorers (like those for zkSync Era or Scroll) may show a "Proven" status instead, meaning the validity proof has been accepted by L1.

What you cannot see directly

• Individual L1 gas cost: The L1 batch fee is split among all transactions in the batch. You see only your share.
• Sequencer ordering details: On most rollups, the sequencer decides transaction order. You cannot verify this from the block explorer alone - you must trust the sequencer's ordering, though fraud proofs (on optimistic rollups) or validity proofs (on ZK rollups) eventually guarantee correctness.
• Cross-rollup activity: If you bridged from one L2 to another, the transaction on the source L2 and the destination L2 will appear on separate explorers. No single explorer tracks both.

When to Use the L1 Explorer Instead

You only need the L1 explorer when:

• You want to verify that your batch was actually posted to L1. Compare the L1 transaction hash from the L2 explorer with the real transaction on Etherscan.
• You are checking whether a withdrawal has completed. The L1 side of a withdrawal is a separate L1 transaction initiated by the rollup's bridge contract after the challenge period or proof verification.
• You suspect the sequencer is not posting data. If the last L1 batch is hours old, the sequencer may be offline - though this is rare on major rollups.

Rolling Summary

A rollup transaction on a block explorer is a decoded reconstruction of compressed data. The key numbers to watch are the L2 execution fee (cheap) and the L1 data fee (variable). Finality takes time - instant on the L2 explorer does not mean instant security. Always check the batch link and L1 transaction hash to confirm your transaction made it to the base layer.

Back to layer 2s