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 Contracts deployed Methodology

## 1. Overview

The TRON contracts deployed metric measures the daily count of new smart contracts deployed on the TRON blockchain. This metric tracks blockchain developer activity and ecosystem growth by counting unique contract deployment transactions that create new smart contract addresses. The calculation aggregates contract creation events by day, ensuring each deployed contract is counted exactly once.

## 2. Data sources

- **TRON contract deployment data**: Raw blockchain data containing contract creation records with deployment timestamps, contract addresses, deployer addresses, and transaction trace information
- **TRON block timestamps**: Block-level timestamp data used to determine when contracts were deployed
- **Transaction traces**: TRON transaction execution traces that track contract deployment operations

## 3. Step-by-step calculation

### Component A: Contract creation extraction
- **Purpose**: Extract and deduplicate contract deployment events from TRON blockchain data
- **Logic**: The system retrieves all contract creation records from TRON blockchain data, selecting the `creation_timestamp` (when the contract was deployed), `contract_address` (the address of the newly created contract), `deployer_address` (the wallet that initiated the deployment), and `creation_trace_address` (transaction trace reference). A distinct clause ensures that each contract deployment is counted only once, preventing duplicate counting if the same deployment appears multiple times in the raw data.
- **Key fields**: `creation_timestamp` for timing, `contract_address` for unique contract identification, `deployer_address` for deployment attribution, and `creation_trace_address` for transaction reference

### Final aggregation
- **Combining components**: The contract creation data is aggregated by day using timestamp truncation to daily boundaries, grouping all deployments that occurred within the same calendar day
- **Time aggregation**: Block timestamps are truncated to day-level granularity, creating daily buckets where `timestamp_trunc(block_timestamp, day)` groups all contracts deployed on the same date
- **Final calculation**: The metric counts the total number of distinct contract deployments per day using a count aggregation. Standard metadata is added including chain identifier as 'tron', market sector as 'blockchains_l1', and business segment as 'blockchain'. The finalize metric macro applies a fill_zeros strategy to ensure consistent daily time series data, creating zero values for days with no contract deployments. Chain availability filtering ensures data quality by including only periods with reliable blockchain data coverage.

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

Unique smart contracts published onchain.

TronTRX

Contracts deployed

Contracts deployed

Competitive landscape