Skip to Content
APIProtocol Revenue Service APIGet TRON Burn / Stake Revenue Statistics

Get TRON Burn / Stake Revenue Statistics

1. Overview & Typical Use

Returns detailed statistics for a selected revenue type (burn or stake), including energy/bandwidth breakdowns, period summaries, revenue shares (Rate), and changes relative to baseline periods (Ratio).

  • Typical use: compare burn revenue vs. stake revenue trends, analyze the composition of each revenue source.
  • When not to use: for a total revenue overview use “Get TRON Protocol Total Revenue”.

2. Endpoint & Authentication

GET /api/consumption/statistic

For Base URL and authentication, see Common Network & Authentication.

3. Request

ParameterTypeRequiredDefaultDescription
sizeintegerNo2000Maximum number of latest daily records included in summaries, up to 2000; applied before timeType aggregation
startintegerNo—Start time, millisecond timestamp
endintegerNo—End time, millisecond timestamp
timeTypeintegerNo0Aggregation of data[]: 0 day, 1 month, 2 quarter, 3 year; does not change top-level comparison periods
typestringNo—Revenue type: burn (burn revenue) or stake (stake revenue)

4. Response

Top-level

FieldTypeRequiredDescriptionUnit/Precision
codeintegerRequiredStatus code; 200 indicates success—
messagestringRequiredRequest status description; "request ok" on success—
statusstringRequiredStatus identifier; "1" on success—
totalintegerRequiredNumber of items returned in data[]—
lastUpdateSecondsintegerRequiredData last updated timeSecond timestamp
dataarrayRequiredRevenue data list; see below—
totalIncomeYesternumberRequiredTotal revenue for the selected type for the current Yester period; see periods belowTRX
totalIncomeMonthnumberRequiredTotal revenue for the selected type for the current Month period; see periods belowTRX
totalIncome3MonthnumberRequiredTotal revenue for the selected type for the current 3Month period; see periods belowTRX
totalIncomeYearnumberRequiredTotal revenue for the selected type for the current Year period; see periods belowTRX
totalIncomeYesterRationumberRequiredChange in totalIncomeYester relative to the same revenue metric in the baseline period; see formula and periods belowDecimal ratio
totalIncomeMonthRationumberRequiredChange in totalIncomeMonth relative to the same revenue metric in the baseline period; see formula and periods belowDecimal ratio
totalIncome3MonthRationumberRequiredChange in totalIncome3Month relative to the same revenue metric in the baseline period; see formula and periods belowDecimal ratio
totalIncomeYearRationumberRequiredChange in totalIncomeYear relative to the same revenue metric in the baseline period; see formula and periods belowDecimal ratio
totalNetIncomeYesternumberRequiredBandwidth revenue for the current Yester period; see periods belowTRX
totalNetIncomeMonthnumberRequiredBandwidth revenue for the current Month period; see periods belowTRX
totalNetIncome3MonthnumberRequiredBandwidth revenue for the current 3Month period; see periods belowTRX
totalNetIncomeYearnumberRequiredBandwidth revenue for the current Year period; see periods belowTRX
totalNetIncomeYesterRatenumberRequiredBandwidth revenue share for the same period: totalNetIncomeYester / totalIncomeYester0–1
totalNetIncomeYesterRationumberRequiredChange in totalNetIncomeYester relative to the same revenue metric in the baseline period; see formula and periods belowDecimal ratio
totalNetIncomeMonthRatenumberRequiredBandwidth revenue share for the same period: totalNetIncomeMonth / totalIncomeMonth0–1
totalNetIncomeMonthRationumberRequiredChange in totalNetIncomeMonth relative to the same revenue metric in the baseline period; see formula and periods belowDecimal ratio
totalNetIncome3MonthRatenumberRequiredBandwidth revenue share for the same period: totalNetIncome3Month / totalIncome3Month0–1
totalNetIncome3MonthRationumberRequiredChange in totalNetIncome3Month relative to the same revenue metric in the baseline period; see formula and periods belowDecimal ratio
totalNetIncomeYearRatenumberRequiredBandwidth revenue share for the same period: totalNetIncomeYear / totalIncomeYear0–1
totalNetIncomeYearRationumberRequiredChange in totalNetIncomeYear relative to the same revenue metric in the baseline period; see formula and periods belowDecimal ratio
totalEnergyIncomeYesternumberRequiredEnergy revenue for the current Yester period; see periods belowTRX
totalEnergyIncomeMonthnumberRequiredEnergy revenue for the current Month period; see periods belowTRX
totalEnergyIncome3MonthnumberRequiredEnergy revenue for the current 3Month period; see periods belowTRX
totalEnergyIncomeYearnumberRequiredEnergy revenue for the current Year period; see periods belowTRX
totalEnergyIncomeYesterRatenumberRequiredEnergy revenue share for the same period: totalEnergyIncomeYester / totalIncomeYester0–1
totalEnergyIncomeYesterRationumberRequiredChange in totalEnergyIncomeYester relative to the same revenue metric in the baseline period; see formula and periods belowDecimal ratio
totalEnergyIncomeMonthRatenumberRequiredEnergy revenue share for the same period: totalEnergyIncomeMonth / totalIncomeMonth0–1
totalEnergyIncomeMonthRationumberRequiredChange in totalEnergyIncomeMonth relative to the same revenue metric in the baseline period; see formula and periods belowDecimal ratio
totalEnergyIncome3MonthRatenumberRequiredEnergy revenue share for the same period: totalEnergyIncome3Month / totalIncome3Month0–1
totalEnergyIncome3MonthRationumberRequiredChange in totalEnergyIncome3Month relative to the same revenue metric in the baseline period; see formula and periods belowDecimal ratio
totalEnergyIncomeYearRatenumberRequiredEnergy revenue share for the same period: totalEnergyIncomeYear / totalIncomeYear0–1
totalEnergyIncomeYearRationumberRequiredChange in totalEnergyIncomeYear relative to the same revenue metric in the baseline period; see formula and periods belowDecimal ratio

Rate, Ratio, and comparison periods

With type=burn, top-level summaries use netBurnIncome and energyBurnIncome; with type=stake, they use netStakeIncome and energyStakeIncome. Total revenue for the selected type is bandwidth plus energy revenue for the same period. data[] still includes both revenue types.

  • Rate = component revenue / total revenue of the selected type for the same period. Returns 0 when that total is zero or negative.
  • Ratio = (current-period revenue − baseline-period revenue) / baseline-period revenue. Total, bandwidth, and energy revenue each use their own current and baseline values. Returns 0 when the baseline is zero, negative, or absent, so 0 alone does not establish that revenue was unchanged.
  • Both are decimal ratios rounded to 6 decimal places using half-up rounding. Multiply by 100 to display percentages. Rate is a 0–1 share; Ratio can be negative or greater than 1.

Let D be the statistics date of the effective end, and T = D + 1 day. If end is later than the latest data-ready time, the endpoint caps it at that time. In the table, day is a daily record’s date; interval endpoints are excluded.

Field suffixCurrent periodBaseline period
YesterDate DD − 1 day
MonthT − 30 days < day < TT − 60 days < day < T − 30 days
3MonthT − 90 days < day < TT − 180 days < day < T − 90 days
YearT − 365 days < day < TT − 730 days < day < T − 365 days

If the selected type’s total revenue on D is zero, negative, or absent, all Yester fields use D − 1 day, with D − 2 days as the baseline. Month, 3Month, and Year are rolling intervals. With complete data, the current boundaries include 29, 89, and 364 daily records respectively; they are not calendar months, quarters, or years.

All top-level summaries use only the latest size daily records retained within start through the effective end, including both dates. The endpoint does not fetch additional baseline data. Incomplete windows sum only the available records; absent records contribute 0. timeType changes the aggregation of data[] only, not the daily records or comparison periods used by top-level summaries.

data[] elements

FieldTypeRequiredDescriptionUnit/Precision
daystringRequiredStatistics dateYYYY-MM-DD
trxPriceInUsdnumberRequiredTRX USD price for the dayUSD
totalIncomenumberRequiredTotal revenueTRX
burnIncomenumberRequiredTotal burn revenueTRX
stakeIncomenumberRequiredTotal stake revenueTRX
energyIncomenumberRequiredTotal energy revenueTRX
netIncomenumberRequiredTotal bandwidth revenueTRX
energyBurnIncomenumberRequiredEnergy burn revenueTRX
energyStakeIncomenumberRequiredEnergy stake revenueTRX
netBurnIncomenumberRequiredBandwidth burn revenueTRX
netStakeIncomenumberRequiredBandwidth stake revenueTRX
burnIncomePercentnumberOptionalBurn income as a share of total revenue for the queried type; code-derived from Greason v5 scan (reproducing sample pending)—
stakeIncomePercentnumberOptionalStake income as a share of total revenue for the queried type; code-derived from Greason v5 scan (reproducing sample pending)—
energyBurnIncomePercentnumberOptionalEnergy burn income share; code-derived from Greason v5 scan (reproducing sample pending)—
energyStakeIncomePercentnumberOptionalEnergy stake income share; code-derived from Greason v5 scan (reproducing sample pending)—
netBurnIncomePercentnumberOptionalBandwidth burn income share; code-derived from Greason v5 scan (reproducing sample pending)—
netStakeIncomePercentnumberOptionalBandwidth stake income share; code-derived from Greason v5 scan (reproducing sample pending)—

5. Errors

For HTTP status codes, see Common Errors. Notes for this endpoint:

  • When size exceeds 2000, it is silently truncated to 2000.
  • Empty result is not an error: no matched records returns 200 + data: [], which is a normal response.