How Often Do L2s Submit Batches to Ethereum
The frequency at which L2s submit batches to Ethereum has no fixed value, typically ranging from a few minutes to an hour, depending on the L2 network, network congestion, and submission strategy. For example, OP Mainnet submits a batch about every 7 minutes on average, while Arbitrum's default configuration sets the batch submission interval at approximately 1440 seconds (about 24 minutes).
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
How Batch Submission Works
The L2 sequencer orders and aggregates user transactions into a "batch", then compresses the data and posts it to the Ethereum mainnet as the data availability layer. This submission operation is carried out by a dedicated "Batch Submitter" (Batcher). Once the data is published on mainnet, the L2 transactions achieve "hard finality".
Submission Frequencies of Different L2s
Case A: OP Mainnet
According to OP Mainnet's official documentation, the average time for a batch to be submitted to Ethereum L1 is about 7 minutes. This includes the full process from batch generation on L2 to data confirmation on L1. Compared to "L2 block confirmation" (about 2 seconds), these 7 minutes represent the moment when the transaction is truly finalized.
Case B: Arbitrum
In Arbitrum's configuration, the batch submission frequency defaults to 120 L1 blocks (approximately 1440 seconds, i.e., 24 minutes). However, the actual frequency is affected by the max-delay parameter – the default maximum delay is 1 hour, meaning the sequencer can wait up to 1 hour before submitting a batch. In high-throughput scenarios, this parameter can be adjusted to 5–15 minutes to balance latency and efficiency.
Case C: Early Optimism Settings
In early versions of Optimism, the batch submission rate was set to once every 30 minutes, meaning L2-to-L1 messages could be delayed by up to 30 minutes before arriving.
Why the Frequency Is Not Fixed
Balancing cost and latency: Submitting a batch requires paying L1 gas fees. Higher frequency means higher costs but faster finality. When gas fees are low, batches may be submitted more frequently to reduce average costs.
Dynamic adjustment strategy: The batch submitter makes dynamic decisions based on L1 congestion, seeking an optimal balance between "delay cost" and "submission cost".
Trigger conditions: Apart from time, batch size can also trigger submission. If the amount of transaction data queued exceeds the maximum size limit (e.g., about 100,000 bytes), the batch will be submitted even if the maximum time interval has not been reached.
A leading global cryptocurrency platform,suitable for both beginners and experienced traders.
New user benefit: 20% off trading fees upon registration!！
Confirmation Completion
To check whether an L2 transaction has been "submitted to Ethereum", you can look up the corresponding L1 hash or batch number on a block explorer such as Etherscan. If the transaction details page shows the "L1 Batch Inclusion" status as complete, the batch has been successfully published onchain. The estimated time for different L2s can be checked on their official explorers (e.g., OP Mainnet's block explorer) by viewing the submission timestamps of specific batches.
