Skip to content
SunSunGo

TRON burn analyzer

How much TRX have you set on fire?

Paste an address. We read the last 500 transactions, add up every Energy and Bandwidth fee you burned, and tell you what renting energy instead would have cost. The number is usually worse than you think.

No address handy? Try this one

  • โœ“ Last 500 transactions
  • โœ“ No wallet connect
  • โœ“ Free, forever, no signup

Three steps to regret

  1. 1. Paste

    An address or a transaction hash. No wallet connect, no signature, no seed phrase. We are not that kind of site.

  2. 2. We count

    Your last 500 transactions get pulled apart fee by fee: Energy burn, Bandwidth burn, and the miscellaneous fees nobody can do anything about.

  3. 3. You wince

    One number for what you burned, one for what renting energy would have cost, and the difference between them. Then you decide.

500

Why 500 transactions and not 30 days?

Because a trading bot can push 500 transactions before lunch and your uncle's wallet can take fourteen months to do the same. A fixed month tells you nothing about either of them. We take a fixed number of transactions and then tell you how long that actually took โ€” so you always know what the window means before you read a single number.

Guides for people who like knowing things

Short, plain, and free of the phrase "revolutionary Web3 paradigm".

Brag about it. Or don't. We made badges either way.

Live PNG badges with your address baked into the image URL. They update themselves. Stick one in a forum signature and let everyone see your burn rate.

Build a badge โ†’

What SunSunGo checks, and why your TRX keeps disappearing

You did not lose that TRX to a bad trade. You lost it to a fee model, one transaction at a time, and nobody ever showed you the total.

The problem, stated plainly

On TRON, a transaction that needs resources you do not have does not fail โ€” it quietly burns TRX instead. Each individual burn looks trivial: a couple of TRX here, thirteen there. Nobody notices a couple of TRX. But wallets do not send one transaction, they send hundreds, and nothing in any wallet interface ever adds it up for you.

SunSunGo adds it up. That is the entire product. Paste an address, get one number for what you burned, one for what renting Energy would have cost instead, and the honest difference between them.

Why the window is 500 transactions and not a month

Every other tool defaults to a fixed period โ€” last 30 days, last week โ€” and that choice quietly ruins the comparison. A market-making bot can push five hundred transactions before lunch. A personal wallet can take over a year to do the same. Telling both of them "here is your last month" produces two numbers that mean completely different things.

So we fix the transaction count instead and derive the time span from the data. Your report opens with a sentence like "Analyzed the last 500 transactions โ€” that is 43 days, from March 2 to April 14." You know exactly what the window is before you read a single figure, and the figures below it are all scoped to that window and nothing else.

What gets counted, and what deliberately does not

TRX gets burned for three separate reasons, and only one of them is fixable by renting Energy. Lumping them together would produce a bigger, more impressive, completely dishonest savings number. So we split them:

  • Energy burn โ€” you did not have enough Energy for a smart contract call. This is the part renting fixes, and the only part that feeds the savings figure.
  • Bandwidth burn โ€” you ran past the free daily allowance. Fixed by staking, or by simply transacting less. Reported separately with its own remedy.
  • Everything else โ€” account activation, memo fees, multisig fees. Shown for completeness, excluded from every savings claim, because nothing you can buy makes them go away.

The number we refuse to inflate

Renting Energy is not always cheaper. If your transactions are small enough, the cheapest rental pack costs more than the TRX you burned, and the correct answer is "do nothing". When that is the case, your report says so instead of showing you a savings figure. We would rather lose a click than tell you something untrue about your own money.

Failed transactions, which are the worst ones

If a contract call runs out of Energy halfway through, it reverts โ€” and the network keeps the fee for the work it already did. You paid, and you got nothing. These show up in your report as their own section with their own total, because they are simultaneously the most avoidable and the most annoying line item on the whole page.

How to use it

  1. Paste a TRON address (starts with T, 34 characters) into the box at the top. Hex addresses starting with 41 work too โ€” we convert them.
  2. Or paste a 64-character transaction hash to see the fee breakdown for one specific transaction.
  3. Read the window sentence first. It tells you what the numbers below mean.
  4. Every headline figure has a Tronscan link next to it. Check our arithmetic against the chain โ€” please do, actually.

What we do not do

No wallet connect. No signature requests. No accounts, no email, no seed phrase, ever. You paste a public address; we read public data. There is nothing here that could move your funds even if we wanted it to.

Where to go next

FAQ

Do I need to connect a wallet?
No. Paste a public address. Nothing is signed, nothing is requested, nothing can be moved.
Why 500 transactions?
It is enough to be statistically meaningful for an active wallet, small enough to fetch quickly, and it makes wallets with wildly different activity levels comparable. The time span it covers is derived and displayed, never assumed.
Is the savings figure a guarantee?
No. It is what standard rental packs would have cost for the Energy your transactions actually consumed, subtracted from what you actually burned. It is arithmetic on historical data, not a prediction, and any forward projection on the page is labelled as such.
Does this work for smart contract addresses?
It reads them fine, but contracts do not rent Energy for themselves โ€” whoever calls the contract pays. We badge contract addresses and suppress the rental pitch accordingly.
How fresh is the data?
Reports are cached for a couple of minutes to be polite to the upstream API. Every report shows the exact timestamp it was fetched.