TRON smart contract energy estimator
Enter a contract, a method and its arguments, and a TRON node simulates the call to report the energy it would use and whether it would revert. Nothing is signed or broadcast.
The same number decides what to rent: energy for the call, delegated to the address that will send it, instead of burning 100 SUN of TRX per unit.
Measured with this estimator on mainnet, 2026-10-01
| Call | Energy |
|---|---|
| USDT transfer to an address that holds USDT | 64,285 |
| USDT transfer to an address with no USDT | 130,285 |
triggerconstantcontract, USDT TR7NHq…Lj6t, transfer of 1 USDT. A contract's energy can change with network parameters; simulate again before a large batch.
What the simulation cannot see
The node runs the call against the chain as it is now. A transfer whose result depends on a later state (another transaction landing first, a price moving) can use more energy when it is actually sent; leave a margin on large batches.
Static arguments only
Addresses, integers, booleans and fixed-size bytes are encoded here. Methods that take strings, dynamic bytes or arrays need a client library; the energy number they report is the same simulation.
FAQ
Does the estimator spend anything?
No. The call is simulated by a node and never broadcast; no key or signature is involved.
Why does the caller address matter?
Many contracts check the caller: its balance, allowance or role. A USDT transfer from an address without the tokens reverts, so the simulation needs the real sender.