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 Transaction count Methodology

## 1. Overview

The TRON transaction count metric measures the total number of unique transactions processed on the TRON blockchain per day. This metric answers the business question "How much transaction activity is occurring on TRON?" and serves as a key indicator of network usage and adoption. The calculation uses an approximate distinct count of transaction hashes grouped by day to efficiently handle large transaction volumes while maintaining accuracy.

## 2. Data sources

The calculation relies on the following data sources:

- **TRON blockchain transaction records**: Complete transaction data from the TRON blockchain including transaction hashes, block timestamps, sender and receiver addresses, gas usage metrics, and fee information
- **Hardcoded bandwidth pricing constants**: Historical bandwidth pricing data for TRON network with two pricing periods (pre and post July 27, 2021) used for fee calculations in the underlying transaction processing

## 3. Step-by-step calculation

### Component A: Transaction data enrichment
- **Purpose**: Processes raw TRON transaction data and enriches it with bandwidth pricing information
- **Logic**: Takes raw TRON blockchain transaction records and joins them with bandwidth pricing data based on block timestamp. The join logic applies the appropriate bandwidth price based on when the transaction occurred, using timestamp ranges to match transactions to pricing periods. All transaction details are preserved including `transaction_hash`, `block_timestamp`, `from_address`, `to_address`, and various gas/energy usage metrics
- **Key fields**: `transaction_hash` for unique identification, `block_timestamp` for temporal grouping, `chain` identifier set to 'tron', and enriched fee calculation fields

### Component B: Daily transaction aggregation
- **Purpose**: Groups transactions by day and counts unique transactions
- **Logic**: Truncates block timestamps to daily granularity using timestamp truncation to create daily boundaries. Groups all transactions by the truncated timestamp and applies approximate distinct counting to the `transaction_hash` field for scalability with large transaction volumes. Assigns standard metric metadata including chain identifier, market sector classification as 'blockchains_l1', and business segment as 'blockchain'
- **Key fields**: `timestamp` (truncated to day), `transaction_count` (approximate distinct count of hashes), and metadata fields for classification

### Final aggregation
- **Combining components**: The enriched transaction data flows directly into the daily aggregation step, with no additional combining required since it's a single data stream
- **Currency conversion**: Not applicable for transaction count metrics - this is a pure count metric
- **Time aggregation**: Daily boundaries are created by truncating block timestamps to day granularity, ensuring all transactions within a 24-hour period are grouped together
- **Final calculation**: The final metric value is the approximate distinct count of transaction hashes per day, enhanced with schema validation, gap filling with zero values for missing days, and chain availability filtering to ensure data quality standards are met

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

Confirmed transactions added to the blockchain.

TronTRX

Transaction count

Transaction count

Competitive landscape