Gravity Alpha batches users' transactions and submits them to Ethereum, paying a share of the transaction fees to Ethereum validators (expense).

Gravity Alpha is an L2 smart contract platform for decentralized applications on Ethereum. Gravity Alpha was founded by Galxe and launched in 2024.

G tokenholders own and govern the protocol. Galxe's investors include Arbitrum Foundation, Multicoin Capital, Dragonfly Capital, etc.

github

twitter

discord

website

Blockchains (L2)

Gravity Alpha Mainnet

# Gravity Alpha Mainnet Block time Methodology

## 1. Overview

Block time measures the average time interval between consecutive blocks produced on the GravityAlpha blockchain on a daily basis. This metric provides insights into the blockchain's performance, network stability, and block production consistency. The calculation analyzes the timestamp differences between consecutive blocks and aggregates them into daily averages.

## 2. Data sources

- **GravityAlpha block headers**: Raw blockchain block data containing timestamps and sequential block numbers from the GravityAlpha network
- **Block timestamp records**: Precise timestamps indicating when each block was produced and added to the blockchain
- **Block sequence data**: Sequential block numbers that establish the chronological order of block production

## 3. Step-by-step calculation

### Component A: Block data extraction
- **Purpose**: Extracts basic block information from raw GravityAlpha blockchain data
- **Logic**: Retrieves block timestamps and block numbers from GravityAlpha block headers. Filters out the genesis block (block 0) since it has no predecessor for time difference calculations. Casts block numbers to integers to ensure proper numerical ordering and calculations.
- **Key fields**: `block_timestamp` (when the block was produced), `block_number` (sequential identifier)

### Component B: Consecutive block pairing
- **Purpose**: Links each block with its immediate predecessor to enable time difference calculations
- **Logic**: Uses a window function to pair each block with the previous block's data, ordered by block number. Creates lagged versions of both timestamp and block number fields. This establishes the relationship needed to calculate time intervals between consecutive blocks.
- **Key fields**: `block_timestamp`, `block_number`, `previous_timestamp`, `previous_block_number`

### Component C: Block time interval calculation
- **Purpose**: Calculates the actual time intervals between consecutive blocks
- **Logic**: Computes timestamp differences between each block and its predecessor, measuring intervals in milliseconds for precision. Only includes blocks that are truly consecutive (where `block_number - previous_block_number = 1`) to avoid gaps from missing or skipped blocks. Truncates block timestamps to daily boundaries to prepare for daily aggregation.
- **Key fields**: `timestamp` (day boundary), `block_time` (millisecond interval)

### Final aggregation
- **Combining components**: Groups block time intervals by day and calculates the average block time for each day
- **Currency conversion**: Not applicable for this timing-based metric
- **Time aggregation**: Daily boundaries are established using timestamp truncation, ensuring all blocks from the same calendar day are grouped together
- **Final calculation**: Computes the mean of all block time intervals within each day to produce a daily average block time in milliseconds. The result includes standard metadata fields including chain identifier (`gravityalpha`), market sector (`blockchains_l2`), and business segment (`blockchain`). Chain availability filtering is applied to ensure data quality standards.

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

avg(block_timestamp - previous_block_timestamp)

Gravity Alpha MainnetG

Block time

Block time

Competitive landscape

Chain breakdown