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 Transactions per second Methodology

## 1. Overview

Transactions per second is defined as the average number of confirmed user transactions added to the MegaETH blockchain each second. Both the network’s throughput and real-time usage are reflected by this metric. By analyzing the rate of transaction execution, the overall activity and capacity utilization of the network are monitored.

## 2. Data sources

- **Blockchain events**: Transaction records extracted from the MegaETH network, covering MegaETH

## 3. Step-by-step calculation

### Component A: Transaction count aggregation

- **Purpose**: To aggregate daily transaction counts from raw transaction records.
- **Logic**: Raw transaction records are ingested from the MegaETH network. Distinct transaction hashes are aggregated and counted on a daily basis to determine the total daily transaction volume.
- **Key fields**: `block_timestamp`, `transaction_hash`

### Component B: Transactions per second calculation

- **Purpose**: To calculate the average throughput per second.
- **Logic**: The total daily transaction count is divided by the number of seconds in a day (86,400) to compute the average transactions per second. This value is calculated for each daily interval.
- **Key fields**: `transaction_count`

### Component C: Finalization and zero-filling

- **Purpose**: To ensure data completeness and schema consistency.
- **Logic**: The calculated transactions per second values are validated against active chain identifiers. Missing days in the time series are filled with zeros to maintain a continuous daily record.
- **Key fields**: `timestamp`, `chain_id`, `transactions_per_second`

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

Average confirmed user transactions added per second.

MegaETHMEGA

Transactions per second

Transactions per second

Competitive landscape