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

The Open Network (TON) is a smart contract platform for decentralized applications (a blockchain). The Open Network was founded by Telegram and launched in 2019.

GRAM holders own and govern the protocol. They currently take (burn) a cut of the total transaction fees paid by users (revenue). The Open Network's investors include KuCoin Ventures, MEXC Ventures, DWF Labs, etc.

governance

github

twitter

etherscan

website

Blockchains (L1)

# TON Block time Methodology

## 1. Overview

Block time measures the average time interval between consecutive blocks on the TON blockchain, expressed in milliseconds. This metric indicates the network's block production speed and consensus efficiency. The calculation uses masterchain blocks (TON's primary coordination layer) to determine authoritative timing intervals, then aggregates these intervals to daily averages for consistent performance monitoring.

## 2. Data sources

- **TON masterchain block data**: Raw block information from TON's masterchain (workchain -1), including block timestamps, sequence numbers (seqno), and metadata
- **Block metadata**: Workchain identifiers and shard information to properly classify blocks within TON's multi-chain architecture

## 3. Step-by-step calculation

### Component A: Masterchain block extraction
- **Purpose**: Identifies the authoritative block sequence from TON's masterchain
- **Logic**: Filters raw TON block data to only include masterchain blocks, identified by `workchain = -1`. Excludes the genesis block by requiring `block_number > 0` since the genesis block has an artificial timestamp at the start of Unix time. Extracts `block_timestamp` and sequence number (`seqno` mapped to `block_number`) for timing calculations
- **Key fields**: `block_timestamp`, `block_number`, `workchain`, `shard`

### Component B: Consecutive block timing
- **Purpose**: Calculates the time interval between each pair of consecutive blocks
- **Logic**: Uses a LAG window function ordered by `block_number` to retrieve the previous block's timestamp and sequence number for each block. Calculates the time difference in milliseconds between current and previous block timestamps. Validates that blocks are truly consecutive by ensuring the `block_number` difference equals exactly 1, preventing gaps in the sequence from skewing timing calculations
- **Key fields**: `block_timestamp`, `previous_timestamp`, `block_time` (in milliseconds)

### Component C: Daily aggregation and standardization
- **Purpose**: Aggregates block times to daily averages with standardized metric formatting
- **Logic**: Truncates block timestamps to daily boundaries and groups all block intervals within each day. Calculates the average `block_time` across all consecutive block pairs for each day. Applies standardized metric schema with TON-specific identifiers including `chain_id` as 'ton', `market_sector_id` as 'blockchains_l1', and `business_segment_id` as 'blockchain'
- **Key fields**: `timestamp` (daily), `block_time` (average), chain and segment identifiers

### Final aggregation
- **Combining components**: Sequential processing where masterchain blocks feed into timing calculations, which then feed into daily aggregation
- **Currency conversion**: Not applicable for this time-based metric
- **Time aggregation**: Daily boundaries using timestamp truncation, with averaging applied to all block intervals within each 24-hour period
- **Final calculation**: The final metric value is the average time in milliseconds between consecutive TON masterchain blocks for each day, processed through the `finalize_metric_block_time` macro for standardization and gap-filling using a 'fill_zeros' strategy

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

avg(block_timestamp - previous_block_timestamp)

TONGRAM

Block time

Block time

Competitive landscape