Decouples execution, sequencing, and verification into specialized roles to maximize hardware utilization. Settles to Ethereum as an L2. Run via a single sequencer model with stateless validation. Uses an EVM-compatible execution environment.

MegaETH is an Ethereum Layer 2 blockchain that targets 100,000+ transactions per second and sub-10ms block times. Its architecture separates sequencers, executors, and verifiers to maximize hardware efficiency and uses an in-memory state structure called SALT (Small Authentication Large Trie) to eliminate disk I/O during execution.

Founded by Shuyao Kong and Namik Muduroglu. MegaETH Labs leads protocol development; the network is intended to be operated by independent sequencers, executors, and verifiers.

website

twitter

Blockchains (L2)

MegaETH

# MegaETH Block time Methodology

## 1. Overview

The average time taken for a new block to be added to the blockchain is measured by block time. The speed at which the network processes transactions and updates its state is reflected by this metric. The operational efficiency and consistency of the consensus and execution environments are evaluated through the tracking of block production intervals.

## 2. Data sources

- **Blockchain events**: Block headers containing block numbers and block timestamps, covering MegaETH

## 3. Step-by-step calculation

### Component A: Block timestamp extraction

- **Purpose**: Retrieve block numbers and their corresponding production timestamps
- **Logic**: Block numbers and block timestamps are extracted from block headers. Only blocks with a block number greater than zero are included in the dataset to ensure the genesis block is excluded from the calculations.
- **Key fields**: `block_timestamp` and `block_number`

### Component B: Block interval calculation

- **Purpose**: Determine the duration between consecutive blocks
- **Logic**: The time difference between each block and its immediate predecessor is calculated in milliseconds. This calculation is performed by ordering blocks sequentially by block number and measuring the elapsed time between consecutive block timestamps.
- **Key fields**: `block_timestamp` and `previous_timestamp`

### Component C: Daily aggregation

- **Purpose**: Calculate the daily average block time
- **Logic**: Block intervals are grouped by day based on the block timestamp truncated to UTC day boundaries. The average block time is calculated for each day. The final values are normalized and formatted to represent the average block time in milliseconds.
- **Key fields**: `block_time`

*This methodology was automatically generated by Token Terminal's methodology analyzer.*

avg(block_timestamp - previous_block_timestamp)

MegaETHMEGA

Block time

Block time

Competitive landscape