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 Average transaction fee Methodology

## 1. Overview

The Tron average transaction fee metric calculates the mean cost per transaction on the Tron blockchain, expressed in USD. This metric answers the question "What does it cost on average to execute a transaction on Tron?" by dividing total daily fees by the total daily transaction count. The calculation accounts for Tron's unique fee structure where transactions consume Energy and Bandwidth resources that can be obtained through staking TRX tokens or by directly burning TRX.

## 2. Data sources

The calculation uses the following raw data sources:

- **Tron transaction records**: Complete blockchain transaction data including receipt information, energy usage, bandwidth consumption, gas prices, transaction hashes, timestamps, and fee details
- **End-of-day price feeds**: Chainlink TRX/USD price feeds for recent data (from March 2021 onwards) combined with CoinGecko daily market data for historical TRX prices (before March 2021)
- **Hardcoded bandwidth pricing**: Time-based bandwidth price tiers reflecting Tron network parameter changes (0.00014 TRX per unit before 2021, 0.001 TRX per unit from July 27, 2021 onwards)

## 3. Step-by-step calculation

### Component A: Transaction data extraction
- **Purpose**: Extract comprehensive transaction information including resource consumption and pricing data
- **Logic**: Process raw Tron transaction records to extract key fields including transaction metadata (`block_timestamp`, `transaction_hash`, `from_address`, `to_address`), fee information (`receipt_info_fee` for total burns), energy consumption data (`receipt_gas_used`, `receipt_info_energy_usage`, `receipt_info_origin_energy_usage`), bandwidth usage (`receipt_info_net_usage`, calculated from `receipt_info_net_fee`), and pricing (`receipt_effective_gas_price` for energy). Join with bandwidth pricing data using timestamp ranges to determine the applicable `bandwidth_price` for each transaction based on when it occurred.
- **Key fields**: `burns` (total TRX burned, normalized by dividing by 1e6), `energy_used`, `bandwidth_used`, `energy_staking_rewards_used`, `bandwidth_staking_rewards_used`, `effective_energy_price` (normalized by dividing by 1e6), `effective_bandwidth_price`

### Component B: Fee calculation by type  
- **Purpose**: Calculate fees from different resource consumption methods in Tron's fee system
- **Logic**: Calculate four distinct fee types aggregated by day. Energy from staking calculates fees as `energy_staking_rewards_used` multiplied by `effective_energy_price`. Bandwidth from staking calculates fees as `bandwidth_staking_rewards_used` multiplied by `effective_bandwidth_price`. Energy supplied by contract calculates fees as `energy_origin_energy_used` multiplied by `effective_energy_price`. Direct TRX burns sum the `burns` field which represents TRX directly burned to pay for energy and bandwidth when staking rewards are insufficient.
- **Key fields**: `fees` (calculated differently for each fee type), `timestamp` (truncated to day), `contract_name` (identifying the fee type)

### Component C: USD conversion
- **Purpose**: Convert TRX-denominated fees to USD using appropriate price feeds  
- **Logic**: Join daily aggregated fees with TRX price data using exact timestamp matching. Use Chainlink price feeds for dates from March 2, 2021 onwards, and CoinGecko daily market data for historical prices before that date. Multiply each `fees` amount by the corresponding `price` to get USD-denominated fees.
- **Key fields**: `fees` (converted to USD), `timestamp`, `price` (TRX/USD exchange rate)

### Component D: Transaction counting
- **Purpose**: Count the total number of unique transactions per day
- **Logic**: Process the same transaction data used for fees, group by day, and apply approximate distinct counting on `transaction_hash` to get daily transaction volumes. This provides the denominator for the average calculation.
- **Key fields**: `transaction_count` (approximate distinct count of transaction hashes), `timestamp`

### Final aggregation  
- **Combining components**: Sum all USD-denominated fees by day across all fee types (energy from staking, bandwidth from staking, energy supplied by contract, direct burns) to get total daily fees. Join this with daily transaction counts using timestamp matching.
- **Currency conversion**: All fees are converted to USD using end-of-day TRX price feeds before aggregation
- **Time aggregation**: All data is grouped by day using timestamp truncation to daily boundaries
- **Final calculation**: Calculate average transaction fee using safe division of total daily fees by total daily transaction count, which handles edge cases where transaction count might be zero

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

TronTRX

Average transaction fee

Average transaction fee

Competitive landscape