How to Check TRON Energy Rental History and Previous Delegations

We run an energy pool at Tronsell, and “how do I check my TRON energy rental history and previous delegations” is one of the questions our users ask most often. In short: if you rent TRON energy from a third-party service, or you have delegated energy to another address yourself, those records live in two different places — the rental platform’s dashboard, and the TRON blockchain.

In this guide, I’ll show you how to check both. I’ll also cover a few key points that most tutorials skip: which on-chain contract types to filter by, and why the blockchain cannot show you the amount you actually paid. The checklist we use in our daily operations is at the end. If you’re new to the topic altogether, our complete guide to TRON energy, TRX fees and transactions covers the basics first.

Energy delegation is recorded on-chain as four contract types

Under TRON’s Stake 2.0 mechanism, energy delegation is not a subscription or an account setting. It is a set of on-chain transactions. Every delegation you have ever sent or received is a transaction of one of the following four contract types:

• DelegateResource — energy or bandwidth delegated to another address
• UnDelegateResource — a delegation cancelled (resources returned to the owner)
• FreezeBalanceV2 — TRX staked to generate resources
• UnfreezeBalanceV2 — staking released, which also auto-cancels every active delegation attached to it

If you have rented energy, the provider almost always carried out the operation through those same two delegation contracts — the owner of the staked assets is the provider, and the receiver of the energy is your wallet address. This is the point most people overlook: you don’t need to log into the provider’s account to find the rental record. On your side, the delegation itself is publicly visible on the chain.

Method 1: Tronscan (easiest, no tools needed)

1. Go to Tronscan.org and paste your wallet address into the search bar.
2. On the address page, switch to the Resources / Staking tab. You’ll see two lists: resources delegated out from your address, and resources delegated in to your address.
3. Each entry shows the counterparty address, the resource type (Energy or Bandwidth), and the amount.
4. To see the full history — including delegations that have already ended — open the Transactions tab and filter by contract type: look for DelegateResource, UnDelegateResource, FreezeBalanceV2, and UnfreezeBalanceV2.

A practical tip from hands-on experience: when you audit, sort the records from oldest to newest first. Delegation lists show the newest records at the top by default, so if a rental happened a few months ago, it’s easy to scroll right past it if you only look at the first screen.

Method 2: Your wallet app (TronLink and similar)

In TronLink, open your address → Resource Management / Staking. This shows your currently active delegations — what’s locked, what’s delegated to whom, and what can be reclaimed. It’s convenient for a quick check, but most wallets only show the current state, not history. For an audit, use Method 1 or Method 3.

Method 3: The TronGrid API (for a complete, verifiable record)

If you want the raw data rather than a website’s rendering of it, TRON’s official API has two endpoints built exactly for this:

• POST /wallet/getdelegatedresource — pass a vfrom and/or vto address, and it returns every active delegation between the two, including balance limits and expiration details.
• POST /wallet/getdelegatedresourceaccountindex — pass one address, and it returns the full index of who that address has delegated to, and who has delegated to it.

This is the same data Tronscan displays, straight from the source. If you ever need to reconcile records with a rental provider and the two sides disagree, this endpoint is what settles it.

On-chain records show the delegation itself, not the price or terms

Make sure you understand this before you rely on on-chain data alone. An on-chain record proves that a delegation existed: it shows which two addresses were involved, how much energy was delegated, and when the delegation started and ended. What it does not show:

• The price you paid. Rental pricing is an off-chain agreement with the provider; no TRON contract has a field for it.
• The provider’s identity. On-chain you see an address, not a brand. Whether that address belongs to Tronsell or to anyone else is something you verify with the provider — the blockchain itself cannot tell you.
• The contract terms. Rental duration, renewal, and refund rules all live in the provider’s system.

So the workflow we recommend is: rely on the blockchain to see which delegation operations took place, and rely on the provider’s dashboard to confirm the amount paid and the rental terms. If the provider’s dashboard ever conflicts with the on-chain delegation records, the on-chain data wins — then ask the provider to explain the difference.

If you haven’t started renting yet, the cost comparison between renting and burning TRX comes up in the FAQ below.

A five-step audit checklist

1. Filter your address transaction history by the four contract types above.
2. For each DelegateResource, note the counterparty address and the amount.
3. Match each one with the corresponding UnDelegateResource — when a delegation ends, confirm the resources actually came back to your side.
4. Look up the receiving address on Tronscan to see whether it’s an exchange hot wallet, a known service address, or something unfamiliar.
5. Compare the on-chain amounts against the provider’s billing records. Mismatches are rare, but when they happen, the on-chain version is the one that counts.

Wrapping up

The key to checking TRON energy rental history is understanding that energy delegations are permanently recorded on the blockchain as standard contract calls — a provider cannot privately hide or tamper with that on-chain record. Tronscan gets you there in two minutes; the TronGrid API gives you the complete, verifiable on-chain evidence; and the provider’s rental dashboard is only for the pricing side, such as the rent you paid. How much energy does a transfer actually need? We broke that down in how much TRON energy you need to send USDT — and why it doubles.

Frequently asked questions

Why doesn’t my finished rental show in the delegation list? 

Delegation lists on Tronscan and in wallets only show what is active right now. Once a rental ends, the record lives in your transaction history under DelegateResource and UnDelegateResource — which is why Method 1 filters by contract type.

Can I see on-chain how much I paid for the energy? 

No. The chain records the delegation itself; the price was agreed with the provider off-chain and stays in their dashboard. That’s exactly why the checklist above reconciles the two sides.

What happens to a delegation if the provider unstakes? 

Unstaking with UnfreezeBalanceV2 automatically cancels every delegation attached to it, and the resources return to the owner. If one of your delegations suddenly disappears, look for that contract type on the provider’s address — it explains almost every “my rental vanished” case.

Is there a cheaper way to cover energy than burning TRX? 

For most transfer volumes, yes — renting. Our guide to renting TRON energy walks through when it beats burning TRX and how the delegation side works in practice.

Sources

1. TRON network documentation, Stake 2.0 (FreezeBalanceV2 / UnfreezeBalanceV2 / DelegateResource / UnDelegateResource contracts), TRON Protocol.
2. TronGrid API reference, getdelegatedresource and getdelegatedresourceaccountindex endpoints, trondocs.org.
3. Tronscan.org — address page resource delegation and transaction-type filters, Tronscan.
4. TRON Improvement Proposal TIP-43 (resource delegation mechanism), TRON DAO GitHub.
5. TronLink wallet resource management documentation, TronLink.
6. Tronsell internal energy pool operations and client reconciliation records, 2025–2026.