Rollup Explorer
Scroll Alpha Testnet is now deprecated.
Please visit our new documentation for the Scroll Sepolia Testnet at https://docs.scroll.io/
The Rollup Explorer displays basic information about Scroll L2 batches and their rollup status.

Rollup Status
There are 3 rollup statuses for Scroll L2 batches in the Alpha Testnet:
Precommittedindicates a block has been included in the Scroll L2 blockchain. Although Precommitted blocks are not yet part of the Scroll L2 canonical chain because they have not been posted on Goerli, users who trust the Sequencer can consider the block to be tentatively finalized.Committedindicates the transaction data of this block has been posted on the rollup contract on Goerli. This ensures that the block data is available, but does not prove that it has been executed in a valid way.Finalizedindicates the correct execution of transactions in this block has been proven by verifying a validity proof on-chain on Goerli. Finalized blocks are considered part of the Scroll L2 canonical chain.
Rollup Table
The table gives information about the rollup status of Scroll L2 batches. The columns are:
Batch Indexshows the batch index. Clicking theBatch Indexwill open the batch detail page.Transactionsshows the number of transactions in the batch.Blocksshows the number of blocks in the batch.Batch Created Timestampshows the time elapsed since the batch is generated.Commit Tx Hashshows the abbreviated transaction hash of the Goerli transaction that posted the transaction data of this Scroll L2 block. Clicking the hash will open a new tab of the Transaction Details page in the Goerli Block Explorer.Commit Timestampshows the time elapsed since the transaction that commits the batch's data to L1.Finalize Tx Hashshows the abbreviated transaction hash of the Goerli transaction that submitted the validity proof of this Scroll L2 batch to the rollup contract on Goerli. Clicking the hash will open a new tab of the Transaction Details page in the Goerli Block Explorer.Commit Timestampshows the time elapsed since the transaction that posts the batch's proof to L1.
Last updated
Was this helpful?
