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 Transactions per second Methodology

## 1. Overview

Transactions per second (TPS) measures the average number of transactions processed by the TON blockchain per second on a daily basis. This metric provides insight into TON's transaction throughput and network activity levels. The calculation takes the total number of unique transactions processed each day and divides by the number of seconds in a day (86,400) to arrive at an average TPS value.

## 2. Data sources

- **TON blockchain transactions**: Native transaction records from the TON blockchain containing transaction hashes, block timestamps, workchain identifiers, account information, and transaction fees
- **TON blockchain blocks**: Block-level data providing timing information for transaction ordering and daily boundary calculations
- **Chain availability data**: Configuration data that defines periods when TON blockchain data is considered complete and reliable for metric calculations

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Extracts all transaction records from the TON blockchain with essential metadata
- **Logic**: Retrieves transaction records from TON blockchain data, capturing the `block_timestamp`, `transaction_hash`, `block_workchain` (as workchain ID), `account`, `total_fees` (as transaction fees), and `account_state_hash_after` for each transaction. This provides the foundation dataset of all TON network activity
- **Key fields**: `block_timestamp` for timing, `transaction_hash` for unique identification, `workchain_id` for workchain classification, `account` for account tracking, and `transaction_fees` for fee analysis

### Component B: Daily transaction count aggregation  
- **Purpose**: Aggregates transaction data by day to count unique transactions per 24-hour period
- **Logic**: Groups transaction data by daily boundaries using timestamp truncation to day level. Counts approximate distinct transaction hashes per day for performance optimization. Assigns static metadata including 'ton' as chain ID, 'blockchains_l1' as market sector, 'blockchain' as business segment, and null product ID. Uses incremental processing with lookback periods to ensure data quality and handle late-arriving transactions
- **Key fields**: `timestamp` (truncated to day), `timestamp_grain` ('day'), `chain_id` ('ton'), `transaction_count` (distinct hash count per day)

### Final aggregation
- **Combining components**: Takes the daily transaction counts from the aggregation component and applies TPS calculation logic
- **Currency conversion**: No currency conversion required as this is a count-based metric
- **Time aggregation**: Maintains daily granularity with each day representing a single TPS calculation period
- **Final calculation**: Divides the daily transaction count by the number of seconds in a day (86,400) using safe division to handle edge cases. Applies finalization logic to ensure schema compliance, validate chain and product IDs, and fill any data gaps with zero values. Filters results based on chain availability periods to exclude data from unreliable time periods, ensuring only high-quality TPS measurements are included in the final metric.

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

Average confirmed user transactions added per second.

TONGRAM

Transactions per second

Transactions per second

Competitive landscape