How Much Did You Spend on TRON Fees? A Monthly Audit with energy_usage_total
How to work out in about an hour how much TRX went to network fees last month: which transaction fields to read, how to split costs into energy, bandwidth and failed transfers, and where the waste usually hides.
In short: to find out how much you spent on TRON fees in a month, add up the fee field (burned TRX) across all your outgoing transactions, and separately total energy_usage_total, which shows how much energy those operations actually consumed. The gap between "energy came from my own stake or a rental" and "energy was bought by burning TRX" is your savings potential. Below: which fields to read, how to build the spreadsheet in about an hour, and which rows usually turn out to be waste.
Why track how much you spend on TRON fees
A single fee is easy to ignore, but with regular USDT TRC-20 transfers it adds up to a real line item. The catch is that wallets do not show a total for a period: you see one transaction at a time, often without a breakdown. Many people only learn the real number when their TRX balance suddenly runs dry.
A monthly audit answers three questions:
- How much TRX was burned on fees in total, and how much per USDT transfer on average.
- What share of transfers ran on your own or rented energy, and what share burned TRX.
- Whether there are anomalies: failed transactions, transfers to empty addresses, unnecessary contract calls.
Which TRON transaction fields show your costs
Everything about the cost of an operation lives in the transaction receipt. The gettransactioninfobyid method returns it (on TronGrid or any full node), and Tronscan shows the same numbers in the resources section of the transaction page. For the audit you need these fields:
- fee: total TRX burned for the transaction, in SUN (1 TRX = 1,000,000 SUN). This is the money you actually paid the network.
- receipt.energy_fee: the part of fee burned to cover missing energy.
- receipt.net_fee: the part of fee burned for bandwidth once the free and staked allowance ran out.
- receipt.energy_usage: energy covered by your own resources, either your stake or delegated (rented) energy.
- receipt.origin_energy_usage: energy paid by the contract owner (for USDT this is usually zero; the sender pays everything).
- receipt.energy_usage_total: the total energy the operation required, from all sources.
- receipt.net_usage: bandwidth covered by the free daily allowance or by stake.
- receipt.result: the execution outcome, such as SUCCESS, REVERT or OUT_OF_ENERGY.
The key pair is energy_usage_total and energy_usage. If they match, the operation ran entirely on your energy and no TRX was burned for energy. If energy_usage is lower, the network "bought" the shortfall by burning TRX, and you will see it in energy_fee.
Why TRX sometimes burns even when you have energy: seven causes explained in TRX burned despite energy.
How to calculate your TRON fees for a month, step by step
- Export the address's outgoing transactions for the month: USDT transfers, TRX transfers and contract calls (swaps, approvals). Incoming transfers do not charge you a fee, so leave them out.
- For each hash, fetch the receipt with gettransactioninfobyid or open the transaction on Tronscan.
- Put these columns in a sheet: date, hash, operation type, result, fee, energy_fee, net_fee, energy_usage, energy_usage_total, net_usage.
- Convert SUN to TRX by dividing fee, energy_fee and net_fee by 1,000,000.
- Compute totals: sum of fee for the month, number of operations, average fee per transfer, and the share of rows where energy_fee is above zero.
How to export an address's history to CSV via Tronscan or the TronGrid API: see TRC20 transaction history export.
Reading the total: four cost buckets
Split the fee total into buckets so you can see right away which spending was necessary and which could have been avoided:
- Energy for USDT transfers (energy_fee on successful token transfers). Usually the biggest bucket for anyone sending without energy.
- Bandwidth (net_fee). A simple transfer takes about 345–360 bandwidth, and the network gives you 600 free per day. Send more than one transfer a day and net_fee shows up.
- Failed transactions (result other than SUCCESS). The USDT did not move, but the TRX burned anyway. Pure loss.
- Other contract calls: swaps, approvals, DeFi activity. Their energy cost depends on the contract.
Benchmarks: is this a normal amount to pay in TRX fees
To judge whether the numbers in your sheet make sense, compare them with verified network parameters:
- A USDT transfer to an address that already holds USDT needs about 64,500–65,000 energy.
- A transfer to an empty address (no USDT) needs roughly twice as much, about 131,000 energy.
- Without your own energy, the network burns about 6.5 TRX for a regular transfer and about 13 TRX for a transfer to an empty address.
- A simple transfer uses about 345–360 bandwidth, against a free allowance of 600 per day.
If your average fee is closer to 13 TRX than to 6.5, most of your transfers go to addresses with no USDT: new customer wallets, fresh exchange deposit addresses. That is not a mistake, but these transfers are worth planning separately because they need twice the energy.
Why an empty address costs twice as much is covered in USDT transfer to an empty wallet.
Where the extra costs usually hide
- Sending transfers one at a time instead of in a batch. Each transfer needs energy, but several back-to-back transfers can be covered by one energy order for the right duration.
- Failed transactions caused by a low fee limit or a lack of energy. A filter on result finds them quickly.
- Repeated approvals and extra contract calls from DApps and bots you forgot about.
- Burning TRX for bandwidth on frequent small TRX transfers long after the daily allowance is gone.
- Energy that was ordered but never used: the rental ended before you sent the transfer.
How much you spent on TRON fees, and what to do about it
Look at the share of rows with energy_fee above zero. If most transfers fall into that group, you are paying the network the full price of energy by burning TRX. There are two ways to fix that: stake TRX and get energy from your stake, or rent energy for specific transfers. Which one works out cheaper depends on the volume and regularity of your transfers and on market conditions at the time you calculate.
How to find the break-even point between staking and renting: see TRX energy: staking vs renting. If your transfers are regular, you can buy TRON energy for the volume you need; the cost depends on the market and the rental period, and delivery speed depends on the network and suppliers.
After you switch to energy, repeat the audit a month later the same way. On successful transfers, energy_usage should equal energy_usage_total and energy_fee should drop to zero. If it does not, look for rows where the transfer went out before the energy reached the address.
TRON fees are invisible one by one but obvious in aggregate. One hour with a spreadsheet each month shows how much TRX burned for nothing.
Want fewer burned TRX in your next report? Calculate the energy for your transfers in the @overtronbot bot.
Read also
How Much a USDT TRC-20 Transfer Costs in 2026: A Formula Built on Live Network Parameters
TRX Fee: How Much TRON Charges for Different Transactions and How to Avoid Spending TRX
TRC20 Transaction History: How to Export to CSV for Bookkeeping with Tronscan and the API
USDT TRC20 Contract Address: How transfer Works and Why It Costs Energy
TRON Testnet: How to Practice USDT Transfers on Shasta and Nile Risk-Free
Received Dirty USDT? What to Do When Tainted Funds Land in Your TRC-20 Wallet
How do I find out how much I spent on TRON fees in a month?
Export the address's outgoing transactions for the month, fetch the receipt for each one (gettransactioninfobyid or the transaction page on Tronscan) and add up the fee field. That is the TRX burned for energy and bandwidth, in SUN; divide by 1,000,000 to get TRX.
What is energy_usage_total in a TRON transaction?
It is all the energy the operation required, from every source: your stake, delegated energy, the contract owner's energy and energy bought by burning TRX. Compare it with energy_usage: if they are equal, no TRX was burned for energy.
What is the difference between fee, energy_fee and net_fee?
fee is the total TRX burned for the transaction. energy_fee is the part for missing energy, and net_fee is the part for bandwidth beyond your free and staked allowance.
Am I charged a fee for incoming USDT transfers?
No. On TRON the sender pays the fee, so your cost audit should only include outgoing transactions and contract calls you initiated.
Why is my TRX fee for a USDT transfer sometimes 6.5 and sometimes 13 TRX?
A transfer to an address that already holds USDT needs about 64,500–65,000 energy, and a transfer to an empty address needs roughly twice that. Without energy, that is about 6.5 and about 13 TRX respectively.
Should failed transactions be counted as costs?
Yes. With REVERT or OUT_OF_ENERGY the USDT does not move, but the TRX for the work already done is burned. These rows are pure loss and worth flagging separately so you can find the cause.
Can I calculate my fee spending without coding?
Yes. Export the address history to CSV from Tronscan and check each transaction's fee on its page. With a few dozen transfers a month this is doable by hand in a spreadsheet; with hundreds, the API is more convenient.
How do I reduce TRON fees after the audit?
If most transfers burn TRX for energy, cover them with energy instead, either by staking TRX or by renting energy for your transfers. Which is cheaper depends on volume, regularity and market conditions at the time you calculate.