Immutable operates a full-stack infrastructure platform for web3 gaming that includes blockchains, namely Immutable zkEVM and Immutable X, and other products, such as Passport and Orderbook. Creators & users sell NFTs on Immutable. They receive royalties from secondary sales (supply-side fees).

Immutable is a platform for building web3 games. Immutable was founded by James Ferguson, Robbie Ferguson, Alex Connolly, and launched in 2018. This dashboard includes data from Immutable Orderbook, Immutable zkEVM, and Immutable X.

IMX holders own and govern the protocol. They currently take a cut of the total trading fees paid by NFT buyers on Immutable Orderbook and the total transaction fees paid by transaction senders on Immutable zkEVM (revenue). Immutable's investors include ParaFi Capital, GameStop Digital Ventures, Fabric Ventures, etc.

governance

github

twitter

discord

etherscan

website

Blockchains (L2)

Immutable

# Immutable Block time Methodology

## 1. Overview

Block time measures the average time interval between consecutive blocks on the Immutable zkEVM blockchain, expressed in milliseconds and aggregated daily. This metric provides insights into the blockchain's performance, consistency, and network health by showing how frequently new blocks are produced. The calculation involves measuring time differences between consecutive blocks and averaging these intervals on a daily basis.

## 2. Data sources

The calculation uses the following raw data sources:
- **Immutable zkEVM block data**: Native blockchain block headers containing timestamps, block numbers, and base fee information
- **Block metadata**: Infrastructure data including block production timestamps and sequential block numbering

## 3. Step-by-step calculation

### Component A: Block data extraction
- **Purpose**: Extract and prepare raw block data for time interval calculations
- **Logic**: Retrieves block timestamps and numbers from Immutable zkEVM blockchain data. Filters out the genesis block (block 0) which has an invalid timestamp at the Unix epoch start. Applies incremental processing logic to only process recent blocks when updating the metric
- **Key fields**: `block_timestamp` (when the block was mined), `block_number` (sequential block identifier)

### Component B: Consecutive block pairing
- **Purpose**: Create pairs of consecutive blocks to enable time interval calculation
- **Logic**: Uses a LAG window function ordered by block number to associate each block with the timestamp of the previous block. This creates pairs of consecutive blocks where each row contains both the current block timestamp and the previous block timestamp
- **Key fields**: `block_timestamp` (current block), `previous_timestamp` (previous block timestamp), `block_number` (for ordering)

### Component C: Block time interval calculation
- **Purpose**: Calculate the time difference between consecutive blocks
- **Logic**: Computes the time difference in milliseconds between each block and its predecessor using timestamp difference functions. Excludes the first block in the sequence since it has no predecessor. Truncates timestamps to daily boundaries for aggregation
- **Key fields**: `timestamp` (daily boundary), `block_time` (interval in milliseconds), `timestamp_grain` (set to 'day')

### Component D: Daily aggregation
- **Purpose**: Average block times within each day
- **Logic**: Groups intervals by daily timestamp boundaries and calculates the average block time for each day. Adds metadata including chain identifier ('Immutable zkEVM'), market sector classification ('blockchains_l2'), business segment ('blockchain'), and product identifier
- **Key fields**: `timestamp` (daily aggregation boundary), `block_time` (daily average in milliseconds), chain and product metadata

### Final aggregation
- **Combining components**: The daily averages are processed through Token Terminal's standard block time finalization macro which applies consistent formatting, validates data quality, and handles missing data
- **Gap filling**: Applies a zero-filling strategy for any missing days to ensure complete time series data
- **Chain filtering**: Applies availability filters based on chain configuration to ensure only supported time periods are included
- **Final calculation**: The final metric represents the average time in milliseconds between consecutive blocks for each day on the Immutable zkEVM network

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

avg(block_timestamp - previous_block_timestamp)

ImmutableIMX

Block time

Block time

Competitive landscape

Chain breakdown