Validators process transactions and receive validator rewards. Super representatives and super representative partners receive voting rewards. TRX stakers receive energy and bandwidth incentives.

Tron is a smart contract platform for decentralized applications (a blockchain). Tron was founded by Justin Sun and launched in 2018.

TRX holders own and govern the protocol. They currently burn all transaction fees paid by users (revenue). It is important to note that the incentives related to energy and bandwidth are effectively returned as revenue, and this is reflected in the earnings.

governance

github

twitter

discord

etherscan

website

Blockchains (L1)

Tron

# Tron Transactions per second Methodology

## 1. Overview

The Tron transactions per second (TPS) metric measures the average number of transactions processed per second on the Tron blockchain over a daily period. This metric provides insight into the network's throughput and activity levels by calculating the daily transaction count divided by the total seconds in a day (86,400). The calculation aggregates all successful and failed transactions to provide a comprehensive view of network utilization.

## 2. Data sources

The calculation relies on the following raw data sources:

- **Tron blockchain transaction records**: Complete transaction data including transaction hashes, block timestamps, sender and receiver addresses, transaction input data, receipt status, and gas/energy usage information
- **Hardcoded bandwidth pricing data**: Historical bandwidth pricing information used for transaction cost calculations (though not directly used in the TPS calculation itself)

## 3. Step-by-step calculation

### Component A: Transaction fact table preparation
- **Purpose**: Processes raw Tron transaction data and enriches it with gas and bandwidth cost information
- **Logic**: Takes raw Tron transaction records and joins them with bandwidth pricing data based on block timestamps. Calculates various gas and energy metrics including `burns`, `energy_used`, `bandwidth_used`, and pricing information. Sets the WTRX token address as a constant and converts gas values from wei to TRX using appropriate decimal adjustments.
- **Key fields**: `block_timestamp`, `transaction_hash`, `chain`, `from_address`, `to_address`, `receipt_status`, and various gas/energy fields

### Component B: Daily transaction count aggregation  
- **Purpose**: Aggregates transactions to daily level and counts distinct transactions per day
- **Logic**: Groups transactions by truncated daily timestamps using `timestamp_trunc(block_timestamp, day)`. Uses `approx_count_distinct(transaction_hash)` to count unique transactions per day, which provides efficient counting for large datasets. Sets metadata fields including `chain_id` as 'tron', `market_sector_id` as 'blockchains_l1', and `business_segment_id` as 'blockchain'.
- **Key fields**: `timestamp` (daily), `chain_id`, `transaction_count`

### Final aggregation
- **Combining components**: The transaction per second calculation takes the daily transaction count from the aggregated data
- **Currency conversion**: Not applicable for this metric as it measures transaction count, not monetary values
- **Time aggregation**: Data is aggregated at daily boundaries using timestamp truncation to day granularity
- **Final calculation**: Divides the daily transaction count by the number of seconds in a day (86,400) using `safe_divide(sum(transaction_count), 86400)` to calculate the average transactions per second for each day. The `safe_divide` function prevents division by zero errors. The finalize macro applies schema validation and fills any missing days with zero values to ensure complete time series data.

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

Average confirmed user transactions added per second.

TronTRX

Transactions per second

Transactions per second

Competitive landscape