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

Astar is a collective driving web3 adoption by connecting people through blockchain technology, business innovation, decentralized applications, and seamless digital experiences in the Polkadot ecosystem. Astar was founded by Sota Watanabe and launched in 2021.

ASTR tokenholders own and govern the protocol. Part of the transaction fees is burned (revenue). Astar’s investors include Binance, Polychain Capital, Crypto.com, etc.

website

twitter

github

discord

Blockchains (L2)

Astar

# Astar Block time Methodology

## 1. Overview

The Astar block time metric measures the average time interval between consecutive blocks on the Astar blockchain, aggregated by day. This metric provides insight into the network's block production consistency and performance. The calculation determines the time difference between each block and its predecessor, then averages these intervals across all blocks produced within each calendar day.

## 2. Data sources

- **Astar blockchain data**: Raw block data from the Astar network containing block metadata
- **Block timestamps**: Precise timestamps when each block was produced on the Astar network  
- **Block numbers**: Sequential block identifiers used to establish chronological order
- **Block author information**: Metadata about which validator or node produced each block

## 3. Step-by-step calculation

### Component A: Block data extraction
- **Purpose**: Retrieves fundamental block information from the Astar blockchain
- **Logic**: Extracts block timestamps, block numbers, and author information from raw Astar blockchain data. Casts timestamps to proper timestamp format and block numbers to integers to ensure consistent data types. Excludes the genesis block (block number 0) since it typically has an invalid timestamp set to the Unix epoch start, which would skew block time calculations.
- **Key fields**: `block_timestamp` (when the block was produced), `block_number` (sequential identifier), `author_id` (block producer)

### Component B: Timestamp pairing
- **Purpose**: Creates pairs of consecutive block timestamps to enable interval calculations
- **Logic**: Orders blocks by their sequential block numbers and uses a LAG window function to associate each block with the timestamp of the immediately preceding block. This creates timestamp pairs that represent consecutive blocks in the blockchain sequence. Filters out the first block in the sequence since it has no predecessor.
- **Key fields**: `block_timestamp` (current block time), `previous_timestamp` (preceding block time), `block_number` (for ordering)

### Component C: Block time interval calculation
- **Purpose**: Computes the actual time intervals between consecutive blocks
- **Logic**: Calculates the millisecond difference between each block timestamp and its predecessor timestamp. Truncates block timestamps to day-level granularity to prepare for daily aggregation. Only includes blocks that have valid predecessor timestamps.
- **Key fields**: `timestamp` (day-truncated timestamp), `block_time` (millisecond interval), `timestamp_grain` (set to 'day')

### Component D: Daily aggregation
- **Purpose**: Aggregates block time intervals into daily average metrics
- **Logic**: Groups all block intervals by calendar day and calculates the arithmetic mean of all block times within each day. Adds standard metadata including chain identifier ('astar') and product identifier ('Astar Substrate'). This smooths out individual block variations to provide a daily performance metric.
- **Key fields**: `timestamp` (daily date), `chain_id`, `product_id`, `block_time` (average milliseconds)

### Final aggregation
- **Combining components**: Daily block time averages are processed through a standardization macro that applies consistent formatting and metadata
- **Currency conversion**: Not applicable for this time-based metric
- **Time aggregation**: Block intervals are aggregated to daily boundaries using calendar day truncation
- **Final calculation**: The final metric represents the average time in milliseconds between consecutive blocks for each calendar day on the Astar network, with chain availability filtering applied to ensure data quality

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

avg(block_timestamp - previous_block_timestamp)

AstarASTR

Block time

Block time

Competitive landscape

Chain breakdown