Validators process transactions and receive validator rewards (supply-side fees).

AVAX is a smart contract platform for decentralized applications (a blockchain). Avalanche was founded by Emin Gün Sirer and launched in 2019.

AVAX holders own and govern the protocol. They currently take (burn) all of the total transaction fees paid by users (revenue). AVAXs investors include a16z, Polychain, Galaxy Digital, etc.

github

twitter

discord

etherscan

website

Blockchains (L1)

Avalanche

# Avalanche Block time Methodology

## 1. Overview

Block time measures the average time interval between consecutive blocks on the Avalanche blockchain, expressed in milliseconds. This metric indicates network performance and consensus efficiency by tracking how frequently new blocks are produced. The calculation determines daily average block production intervals by measuring timestamp differences between sequential blocks and aggregating these intervals across each day.

## 2. Data sources

- **Avalanche blockchain data**: Block headers and metadata from the Avalanche network containing block numbers, timestamps, and production records
- **Block timestamps**: Precise timestamp records for when each block was produced on the Avalanche network
- **Block sequencing data**: Block numbering system that allows ordering of blocks chronologically

## 3. Step-by-step calculation

### Component A: Block data extraction
- **Purpose**: Retrieves fundamental block information from Avalanche blockchain
- **Logic**: Extracts block timestamps and block numbers from Avalanche block records. Excludes the genesis block (block number 0) since it has a timestamp at the start of Unix time which would skew calculations. For incremental updates, applies a lookback buffer to ensure data completeness across partition boundaries.
- **Key fields**: `block_timestamp` for when blocks were produced, `block_number` for sequential ordering

### Component B: Temporal sequencing
- **Purpose**: Establishes previous block timestamp for interval calculation
- **Logic**: Uses a lag window function to retrieve the timestamp of the immediately preceding block for each current block. Orders blocks by block number in ascending sequence to ensure proper chronological pairing. This creates pairs of consecutive blocks needed for time interval calculation.
- **Key fields**: `block_timestamp` for current block, `previous_timestamp` for the preceding block, `block_number` for ordering

### Component C: Block time interval calculation
- **Purpose**: Computes actual time differences between consecutive blocks
- **Logic**: Calculates timestamp differences in milliseconds between each block and its predecessor. Excludes the first block in the sequence since it has no previous timestamp. Truncates block timestamps to daily boundaries for subsequent aggregation.
- **Key fields**: `block_time` as millisecond intervals, `timestamp` truncated to daily boundaries

### Final aggregation
- **Combining components**: Groups block time intervals by daily timestamp boundaries
- **Time aggregation**: Averages all block time intervals within each calendar day to produce daily average block time
- **Currency conversion**: Not applicable for this infrastructure metric
- **Final calculation**: Applies averaging function across all block intervals for each day, then uses the finalize metric macro to add standard blockchain metadata including chain identifier as 'avalanche', market sector as 'blockchains_l1', and business segment as 'blockchain'. Uses fill zeros strategy for any missing daily values to ensure continuous time series data.

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

avg(block_timestamp - previous_block_timestamp)

AvalancheAVAX

Block time

Block time

Competitive landscape