Aleph Zero EVM is powered by Arbitrum's AnyTrust protocol which uses a data availability committee (DAC) to store raw transaction data.

Aleph Zero EVM is an Ethereum layer 2 powered by Arbitrum Orbit tech stack. This dashboard does not include Aleph Zero WASM data.

AZERO tokenholders own and govern the protocol.

github

twitter

discord

website

Blockchains (L2)

Aleph Zero EVM

# Aleph Zero EVM Block time Methodology

## 1. Overview

The Aleph Zero block time metric measures the average time between consecutive blocks produced on the Aleph Zero EVM blockchain, aggregated daily. This metric provides insights into the blockchain's performance consistency and throughput characteristics by tracking how long it takes on average to produce each new block. The calculation involves analyzing the timestamp differences between sequential blocks and averaging these intervals by day.

## 2. Data sources

- **Blockchain block data**: Raw block information from Aleph Zero EVM blockchain nodes, including block timestamps and sequential block numbers
- **Block metadata**: Timestamp records indicating when each block was produced and confirmed on the Aleph Zero EVM network

## 3. Step-by-step calculation

### Component A: Block data extraction
- **Purpose**: Retrieves fundamental block information needed for time interval calculations
- **Logic**: Extracts block timestamps and block numbers from Aleph Zero EVM blockchain data. The `block_timestamp` field contains the exact time when each block was produced, while `block_number` provides the sequential ordering of blocks in the chain. Block numbers are cast to integers to ensure proper numerical ordering for subsequent calculations.
- **Key fields**: `block_timestamp` (when the block was created), `block_number` (sequential block identifier)

### Component B: Block interval preparation
- **Logic**: Uses a lag window function to access the timestamp of the previous block for each current block. Blocks are ordered by `block_number` in ascending order to ensure chronological sequence. This creates a dataset where each row contains both the current block timestamp and the previous block timestamp, enabling time difference calculations.
- **Key fields**: `block_timestamp` (current block time), `previous_timestamp` (previous block time from lag function)

### Component C: Block time calculation
- **Purpose**: Calculates the actual time intervals between consecutive blocks
- **Logic**: Computes the millisecond difference between each block timestamp and its previous block timestamp using timestamp difference functions. Filters out records where no previous timestamp exists (typically the first block in the dataset). Truncates timestamps to day boundaries to prepare for daily aggregation.
- **Key fields**: `block_time` (millisecond interval between blocks), `timestamp` (daily truncated timestamp)

### Component D: Daily aggregation
- **Purpose**: Aggregates individual block times into daily average metrics
- **Logic**: Groups block time measurements by day and calculates the average block time for each day. Assigns metadata including chain identifier as 'Aleph Zero EVM', market sector as 'blockchains_l2', and business segment as 'blockchain'. Sets product identifier to null since this is a chain-level metric rather than a specific product metric.
- **Key fields**: `block_time` (daily averaged block time in milliseconds), `timestamp` (daily aggregation boundary)

### Final aggregation
- **Combining components**: Daily averaged block times are processed through the `finalize_metric_block_time` macro which standardizes the metric format and applies any necessary data quality checks or transformations
- **Time filtering**: Results are filtered to exclude any future dates beyond September 17, 2025, ensuring the metric only includes historical and current data
- **Data quality**: The 'fill_zeros' strategy is applied to handle any gaps in the daily time series, though the specific implementation depends on the macro logic
- **Final calculation**: The final metric represents the average time in milliseconds between consecutive blocks for each day on the Aleph Zero EVM blockchain

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

avg(block_timestamp - previous_block_timestamp)

Aleph Zero EVMAZERO

Archived

Block time

Block time

Competitive landscape

Chain breakdown