Get Contract Energy Consumption Data

1. Overview & Typical Use

Returns energy statistics for contracts, including total energy consumption, source distribution, and contract rankings.

Typical use: analyzing per-contract energy consumption, viewing the energy consumption leaderboard.
When not to use: to view daily aggregated energy consumption trends across the network, use “Get Energy Consumption Distribution”.

GET /api/energydailystatistic

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

Parameter	Type	Required	Default	Description
`day`	integer	No	Latest statistics period	Current timestamp in milliseconds
`limit`	integer	No	`10`	Number of results, maximum `50`

Top-level

Field	Type	Required	Description	Unit/Precision
`totalTrigger`	integer	Required	Total trigger transactions for the day	—
`totalCallerAmount`	integer	Required	Total number of callers for the day	—
`totalEnergy`	integer	Required	Total energy consumed for the day	—
`total`	integer	Required	Total number of matched contracts	—
`lastUpdateSeconds`	integer	Required	Data update time	Unix timestamp in seconds
`data`	array	Required	Contract energy consumption list, see below	—

data[] element

Field	Type	Required	Description	Unit/Precision
`contract_address`	string	Required	Contract address	—
`total_energy`	integer	Required	Total energy consumed by this contract	—
`energy`	integer	Required	Energy from staking	—
`contract_supplied`	integer	Required	Energy supplied by the contract itself	—
`trx`	integer	Required	Energy paid by burning TRX	—
`name`	string	Required	Contract name	—
`total_energy_percent`	number	Required	This contract’s share of total energy	—
`tag1`	string	Optional	Contract tag	—
`tag1Url`	string	Optional	URL corresponding to the contract tag	—
`blueTagUrl`	string	Optional	Contract official website URL	—
`isToken`	boolean	Required	Whether it is a token contract	—
`publicTagDesc`	string	Optional	Public tag description	—
`risk`	boolean	Required	Risk flag	—
`vip`	boolean	Required	Whether it is a VIP contract	—

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