TRON bandwidth checker
See TRON bandwidth remaining on a T-address, how it differs from energy, and when a short meter burns TRX as NetFee.
Bandwidth is the size budget, energy is the compute budget
Every TRON transaction occupies bytes. Bandwidth is the resource that pays for those bytes. A simple TRX transfer can complete on bandwidth alone. A USDT TRC20 transfer is a smart-contract call: it still uses bandwidth for the envelope, but the expensive part is energy.
If you only watch energy, a native TRX send can still fail or burn TRX because BandwidthLimit minus BandwidthUsed was too small. The bandwidth checker exists so that failure mode has its own screen.
How to read BandwidthLimit and BandwidthUsed
getaccountresource returns BandwidthLimit (sometimes labelled net limit in older docs) and BandwidthUsed. Remaining bandwidth is the difference. Free daily bandwidth also exists for accounts that are not frozen for this resource; it regenerates on a schedule and is easy to exhaust with a burst of tiny transfers.
Staking or freezing TRX specifically for bandwidth raises the limit in a more stable way. That is a different freeze target than energy. People who freeze “for fees” without choosing the resource often mint the one they did not need.
NetFee is the burn when bandwidth runs out
When remaining bandwidth cannot cover the transaction size, TRON burns TRX as a network fee instead. That burn is not the same as the energy burn that covers a contract call. Explorers may show both, which is why “I got charged TRX” needs a second look at which meter was empty.
A USDT send that also lacks energy can burn TRX for compute and still consume bandwidth. Fixing only energy leaves the NetFee path open. Check both resources on the sending account before retrying.
What this screen will not tell you
Bandwidth remaining is not a phishing detector and not a blacklist. An address with huge bandwidth can still be a drain destination. An address with zero bandwidth can still be a cold storage wallet that simply has not been used this week.
The checker does not simulate the exact byte size of an unsigned transaction in your wallet. Use the reading as a go / no-go for “is the tank empty,” then confirm in TronLink’s resource tab before a large native TRX batch.
When bandwidth is the real blocker
If TRX transfers fail while USDT would have failed for a different reason, start here. Stake for bandwidth, wait for daily regeneration if you only need a small send, or stop spraying dust transactions that chew the free quota. Then re-run the same T-address.
Help stays at @wholetron with public data only. This site never asks for a seed phrase. Optional deep scan remains a read-only ~2–3 TRX confirmation, not a bandwidth top-up.
FAQ
Is bandwidth the same as energy?
No. Bandwidth pays for transaction bytes. Energy pays for smart-contract compute such as USDT TRC20.
What fields should I look at?
BandwidthLimit and BandwidthUsed from getaccountresource. Remaining bandwidth is Limit minus Used.
Why did my TRX transfer burn a fee?
When bandwidth is insufficient, TRON burns TRX as NetFee to cover the transaction size.
Does USDT TRC20 need bandwidth too?
Yes, for the transaction envelope. The large cost is still energy. Short bandwidth can add a TRX NetFee on top.
How do I raise bandwidth?
Stake or freeze TRX targeting bandwidth, or wait for free daily bandwidth to regenerate if the send is small.
Can this checker add bandwidth to my account?
No. It only reads public resource fields. Staking and rentals happen in your wallet or a market you choose.
Do I connect a wallet for the free bandwidth check?
No. Paste the T-address. Never share a seed phrase. Optional deep scan is read-only and about 2–3 TRX.