TRON energy checker
Paste a T-address to see remaining TRON energy from EnergyLimit and EnergyUsed before a contract call or USDT TRC20 transfer.
Read remaining energy as a subtraction
EnergyLimit is the ceiling the account can spend on contract compute in the current window. EnergyUsed is what it has already spent. Remaining energy is Limit minus Used. A wallet that only prints one of those two numbers is hiding the only figure that matters for the next send.
The free checker pulls getaccountresource for the pasted T-address. Nothing is signed. The result is a point-in-time snapshot: a USDT transfer, a rental credit, or an undelegate can move both numbers within a minute.
Why the meter moves after every TRC20 call
A successful USDT TRC20 transfer consumes energy on the sender. A failed call can still consume a slice if the node executed part of the contract before aborting. That is why “I had enough a minute ago” is a weak argument — re-read EnergyUsed after every attempt.
Delegated energy from a rental or a friend raises EnergyLimit until the lock expires or the delegator undelegates. When that credit drops off, Limit falls even if you did not send anything. Sudden drops are usually expiry, not a hack of your keys.
Energy does not describe the counterparty
Checking your own sending account tells you whether the next contract call can complete without burning TRX. Checking someone else’s address tells you their resource state, which is useful for support and for spotting empty-fee traps, but it is not a character reference.
Do not treat a fat energy tank as proof that an OTC desk is legitimate. Do not treat an empty tank as proof of fraud. Combine the resource read with the actual destination, the contract string, and how the payment request reached you.
Pair the energy read with bandwidth
Contract calls need energy; the transaction envelope still needs bandwidth. If bandwidth is also short, the node can burn TRX as NetFee even when energy looks healthy. Read both meters before you blame “out of energy” for a native TRX send that never touched a contract.
TronLink’s resource tab lists Energy and Bandwidth on separate rows. If this checker and TronLink disagree, wait a few seconds for the node to catch up, then compare the full T-address — a single-character paste error produces a different account entirely.
What to do when remaining energy is thin
Stake TRX for energy under Stake 2.0, wait for an existing delegation, or rent a short burst from a market you already use. Then run the same address through this checker again. Planning around ~65k energy for a typical USDT TRC20 transfer is reasonable; treating 65k as a guaranteed on-chain constant is not.
Optional deep scan can add a read-only look at related resource and transaction context for about 2–3 TRX. It never asks for a seed phrase. For a confusing public snapshot, ask @wholetron with the address only.
FAQ
What is remaining energy?
EnergyLimit minus EnergyUsed from getaccountresource. That remainder is what the account can still spend on contract compute.
Does a high EnergyLimit mean the address is safe?
No. It only means the account has staked, frozen, or received delegated energy. Safety of a payment is a separate question.
Why did energy drop without a transfer?
Delegated or rented energy expired, the delegator undelegated, or you unstaked. Limit falls when the credit is withdrawn even if you sent nothing.
Does the checker need my wallet?
Not for the free screen. Paste the public T-address. Optional deep scan is a read-only confirmation around 2–3 TRX and never asks for a seed phrase.
Can I check someone else’s energy?
Yes. Resource fields are public. That still does not tell you who controls the keys or whether you should pay them.
Is ~65k energy enough for USDT TRC20?
It is a common estimate for a typical transfer, not a protocol guarantee. Re-check remaining energy on the sending account right before you sign.
Where do I get help reading a result?
Ask @wholetron with the T-address or tx hash. Never send a seed phrase.