Starknet is a Validity-Rollup (ZK-Rollup) Layer 2 network that operates on top of Ethereum, enabling dApps to massively scale without compromising on security. It achieves this by bundling transactions into an off-chain computed STARK proof. This proof is then submitted to Ethereum as a single transaction, resulting in significantly higher throughput, faster processing times, and much lower costs, all while retaining the robust security of the Ethereum settlement layer.

Starknet aims to be governed by a decentralized, community-driven process centered around STRK token holders. While StarkWare originally developed the technology, the network is transitioning to a completely decentralized model where the broader community makes decisions regarding protocol upgrades, development, and the future of the network.

Starknet is a Layer 2 that uses STARK technology to validate off-chain transactions, enabling unlimited scale while preserving Ethereum's security and decentralization.

github

twitter

discord

etherscan

website

governance

Blockchains (L2)

Starknet

# Starknet Block time Methodology

## 1. Overview

Block time measures the average time interval between consecutive blocks on the Starknet network, expressed in milliseconds and aggregated daily. This metric indicates network performance and block production consistency. The calculation determines the time difference between each block and its predecessor, then computes the daily average across all block intervals within each day.

## 2. Data sources

- **Starknet blockchain data**: Raw block information from the Starknet network including block timestamps and sequential block numbers
- **Block metadata**: Timestamp data for each block produced on the Starknet chain, used to calculate production intervals

## 3. Step-by-step calculation

### Component A: Block data extraction
- **Purpose**: Extract fundamental block information from Starknet blockchain data
- **Logic**: Retrieve all blocks from Starknet network data, capturing both the `timestamp` when each block was produced and its sequential `block_number`. The genesis block (block 0) is explicitly excluded since it has a timestamp at the start of Unix time which would create misleading block time calculations
- **Key fields**: `block_timestamp` containing when each block was produced, `block_number` for sequential ordering

### Component B: Time interval calculation
- **Purpose**: Calculate the time difference between consecutive blocks
- **Logic**: Use a lag window function to retrieve the previous block's timestamp for each block when ordered by block number. Calculate the millisecond difference between each block's timestamp and its predecessor's timestamp using timestamp difference functions. Blocks without a previous timestamp (the first block after genesis) are excluded from calculations
- **Key fields**: `block_timestamp` for current block time, `previous_timestamp` from the lag function, `block_time` as the calculated millisecond difference

### Component C: Daily time aggregation  
- **Purpose**: Group block intervals by day and calculate daily averages
- **Logic**: Truncate block timestamps to daily granularity and group all block time intervals within each day. Calculate the average block time in milliseconds for each day across all block intervals that occurred on that day
- **Key fields**: `timestamp` truncated to day level, `block_time` containing the calculated interval for averaging

### Final aggregation
- **Combining components**: All daily block time calculations are processed through the finalize metric block time macro
- **Currency conversion**: Not applicable for time-based metrics
- **Time aggregation**: Daily boundaries are established by truncating timestamps to day granularity, with all block intervals within each day averaged together
- **Final calculation**: The final metric value represents the average time in milliseconds between consecutive blocks produced on each day, standardized with chain metadata including chain identifier as 'starknet', market sector as 'blockchains_l2', and business segment as 'blockchain'

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

avg(block_timestamp - previous_block_timestamp)

StarknetSTRK

Block time

Block time

Competitive landscape

Chain breakdown