Validators process transactions and receive fees from users (supply-side fees).

Sei is a Layer 1 blockchain built for fast, low-cost financial transactions. It combines the security and reliability of Ethereum with the high performance of Solana. To date, Sei has processed billions of transactions across more than 90 million wallets. The project is backed by leading investors, including Multicoin Capital, Jump, Coinbase Ventures, and Circle Ventures. Token Terminal exclusively tracks Sei EVM data.

SEI holders own and govern the protocol. They currently do not take a cut of the transaction fees paid by users (revenue). Sei's investors include Multicoin Capital, Coinbase, etc.

github

twitter

discord

website

Blockchains (L1)

Sei Network

# Sei Network Block time Methodology

## 1. Overview

Block time measures the average time required for a new block to be added to the Sei Network. It reflects the operational speed of Sei EVM and the frequency at which the network processes transactions and updates its global state. This metric serves as a key indicator of network performance, latency, and throughput efficiency for institutional analysis.

## 2. Data sources

- **Blockchain events**: Block headers and timestamps from Sei EVM, covering Sei Network
- **External data**: None required for this metric

## 3. Step-by-step calculation

### Component A: Sei EVM block data extraction

- **Purpose**: Retrieve the fundamental timing data for every block produced on the network
- **Logic**: Block numbers and their corresponding timestamps are extracted from Sei EVM block headers. The genesis block is explicitly excluded from the calculation to prevent the initial Unix epoch timestamp from distorting the results.
- **Key fields**: `block_number` (sequence identification) and `block_timestamp` (timing)

### Component B: Production interval calculation

- **Purpose**: Determine the elapsed time between sequential blocks
- **Logic**: A comparison is performed between the timestamp of each block and the timestamp of the immediately preceding block. The difference between these two values is calculated in milliseconds. The logic ensures that only consecutive blocks (where the difference in block height is exactly one) are utilized to maintain the integrity of the timing intervals.
- **Key fields**: `block_timestamp` and `previous_timestamp`

### Component C: Daily average aggregation

- **Purpose**: Standardize the block time data into a daily representative metric
- **Logic**: All individual block production intervals calculated in the previous step are grouped by UTC day. An arithmetic mean is applied to these intervals to determine the average block time for each 24-hour period. The final values are maintained at a daily granularity to provide a consistent view of network performance over time.
- **Key fields**: `timestamp` (UTC day) and `block_time` (average milliseconds)

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

avg(block_timestamp - previous_block_timestamp)

Sei NetworkSEI

Block time

Block time

Competitive landscape

Chain breakdown