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

Fantom is a smart contract platform for decentralized applications (a blockchain). Fantom was founded by Dr. Ahn Byung Ik and launched in 2019.

FTM holders own and govern the protocol. They currently take a cut of the total transaction fees paid by users (revenue). Fantom’s investors include DHVC, Arrington XRP Capital, 8 decimal Capital, etc.

github

twitter

discord

etherscan

website

Blockchains (L1)

Fantom

# Fantom Block time Methodology

## 1. Overview

The Fantom block time metric measures the average time interval between consecutive blocks on the Fantom blockchain, expressed in milliseconds and aggregated daily. This metric provides insight into the network's block production performance and consistency. The calculation determines how long it takes, on average, for the Fantom network to produce each new block by measuring the time differences between consecutive block timestamps and averaging these intervals by day.

## 2. Data sources

The metric is calculated using raw Fantom blockchain data:
- **Fantom block headers**: Block timestamp and block number data from the Fantom network
- **Blockchain timing data**: Exact timestamps when each block was mined/validated on the Fantom network
- **Block sequence data**: Sequential block numbering to establish correct chronological ordering

## 3. Step-by-step calculation

### Component A: Block data extraction
- **Purpose**: Retrieves fundamental block timing data from the Fantom blockchain
- **Logic**: Extracts distinct block records containing timestamps and block numbers. Filters out the genesis block (block number 0) since it has an incorrect timestamp set to the Unix epoch start, which would skew calculations. Only includes blocks with block numbers greater than 0 to ensure accurate timing measurements.
- **Key fields**: `block_timestamp` (when the block was created), `block_number` (sequential block identifier)

### Component B: Consecutive block pairing
- **Purpose**: Pairs each block with its immediate predecessor to enable interval calculation
- **Logic**: Uses a window function to retrieve the previous block's timestamp for each block, ordered by block number in ascending order. This creates pairs of consecutive blocks needed to calculate time differences. Blocks are ordered sequentially to maintain chronological accuracy.
- **Key fields**: `block_timestamp` (current block time), `previous_timestamp` (preceding block time), `block_number` (for ordering)

### Component C: Block time interval calculation
- **Purpose**: Calculates the actual time difference between consecutive blocks
- **Logic**: Computes the millisecond difference between each block's timestamp and its predecessor's timestamp. Truncates block timestamps to daily boundaries for subsequent aggregation. Filters out the first block in the sequence since it has no predecessor and cannot have an interval calculated.
- **Key fields**: `timestamp` (day-level timestamp), `block_time` (interval in milliseconds)

### Component D: Daily aggregation and metadata
- **Purpose**: Aggregates block times by day and adds required metadata fields
- **Logic**: Groups block time intervals by daily timestamp boundaries and calculates the average block time for each day. Adds standard categorization fields including chain identifier, market sector, and business segment. Sets product identifier to null since this is a chain-level metric rather than a product-specific one.
- **Key fields**: `timestamp` (daily boundary), `block_time` (average milliseconds), `chain_id` ('fantom'), `market_sector_id` ('blockchains_l2'), `business_segment_id` ('blockchain')

### Final aggregation
- **Combining components**: The daily averaged block times flow through a finalization macro that standardizes the metric format and applies consistency checks
- **Currency conversion**: Not applicable for this timing-based metric
- **Time aggregation**: Block times are aggregated to daily averages, with timestamps truncated to day-level boundaries
- **Final calculation**: The final metric represents the average number of milliseconds between consecutive blocks on the Fantom network for each day, providing a measure of block production speed and network performance consistency

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

avg(block_timestamp - previous_block_timestamp)

FantomFTM

Archived

Block time

Block time

Competitive landscape