How to Read TRON Transaction Details on TronScan

Every TRON transfer leaves a public record. Learning to read a transaction page on TronScan lets you verify USDT payments, debug failures, and provide support teams with precise evidence.

This guide decodes the fields you see on a typical TRC-20 USDT transaction.

Open the transaction

1. Go to tronscan.org
2. Paste txid (64-character hash) in search
3. Open transaction detail page

TronScan guide for basics.

Header summary

For USDT transfer, To is often the USDT contract address, not final recipient — read logs for real recipient.

Fee section

• Fee (TRX) — TRX burned or paid
• Energy Fee / Energy Usage — contract execution cost
• Bandwidth — transaction size cost

High Energy on failed tx still charged — transaction failed.

Token transfer tab

User-friendly view:

From: TSender...
To: TRecipient...
Amount: 100 USDT
Token: Tether USD (USDT)
Contract: TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t

Verify contract matches official Tether USDT — fake USDT.

Event logs (advanced)

Raw Transfer event:

• topic1 — from address (indexed)
• topic2 — to address (indexed)
• data — amount in 6 decimal base units for USDT

Developers decode for payment APIs.

Internal transactions

Contract calls may trigger sub-calls — internal tab shows TRX or token movements inside execution. Useful for complex SunSwap swaps.

Failed transaction fields

Look for:

• result: FAILED
• resMessage — sometimes hex revert reason
• Energy consumed without token transfer

Common: OUT_OF_ENERGY, REVERT.

Confirming payment as recipient

Checklist:

• [ ] Result = SUCCESS
• [ ] USDT contract = TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t
• [ ] To address = your T...
• [ ] Amount matches invoice (watch decimals)

Share txid link with payer as proof.

Confirming send as sender

Same checks for recipient address — typos show SUCCESS but wrong To in logs.

Export and support

• Copy txid URL for exchange support
• Screenshot timestamp + amount + addresses
• Report scams if fraudulent counterparty

API equivalent

Developers: verify transaction API returns same receipt data programmatically.

FAQ

Where do I see if USDT was sent in a transaction?

On the transaction page, open Event Logs or Token Transfer section — look for Transfer on contract TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t.

What does Bandwidth and Energy on the tx page mean?

Resources consumed executing the transaction. USDT transfers primarily use Energy; simple TRX sends use Bandwidth.

Multiple tokens in one tx?

Possible in complex contract interactions — expand all transfer rows.

Transaction succeeded but no USDT?

May be TRX-only tx or different token contract — read token transfer section carefully.

Hex addresses in logs?

TronScan converts to T... in UI — hex is internal representation.