One rental, three verifiable mainnet transactions
This operator-provided case was checked against TRON Mainnet transaction bodies and receipts on 6 November 2026. The payment sender, Energy recipient and later contract caller are the same address.
Updated 6 November 2026
Paying wallet / Energy recipient: TGLgVCbyeogQ4HzWssFt8pGgvmWtKKDeFi
01 / Payment
TransferContract · SUCCESS · 2 TRX
- Block time (UTC)
- Block
- 87742247
- Transaction hash
- e7b4656d189627f03e8f6e6418be94ccb97d286ec1992a97bbd68ce8665aae0d
02 / Energy delegation
DelegateResourceContract · SUCCESS · ENERGY
- Block time (UTC)
- Block
- 87742249
- Transaction hash
- 7b8feb69474c142fa08432fdc2c0d0fd81088536efe37c98d706088517cfe92b
03 / Resource use
TriggerSmartContract · SUCCESS · 46,217 Energy
- Block time (UTC)
- Block
- 87742263
- Transaction hash
- 798c9a1332c4a8d35c241b4e41cbac1cb83afd437fc33f0e2a1de9bd7cf206ee
What the records establish
- The first transaction is a 2 TRX native transfer to the official TronZero payment address.
- The second transaction is an ENERGY resource delegation to the same paying wallet. Its inclusion time is six seconds after the payment inclusion time.
- The third transaction is a successful smart-contract call from the same wallet. Its receipt reports 46,217 Energy used.
What this case does not establish
These timestamps are block inclusion times, not browser confirmation or monitoring timestamps. Six seconds is the observed interval for this case, not a delivery SLA. The delegation contract records a staked TRX balance, not a direct 65,000-Energy amount. The case does not prove zero total fees, guarantee every future order, or document buyback yield payments.
Source: TRON Mainnet FullNode API; independently inspect each transaction above.