WTRX means Wrapped TRX: a TRC20 token representation of TRX on the TRON network. Native TRX and WTRX are different entries to read in an explorer. Seeing WTRX in a token list does not establish that the same number is available as native TRX for a different operation.
This beginner guide identifies the specific Mainnet contract and reads one real deposit record. It is a read-only explanation, not instructions to approve a spending contract, connect a wallet or send funds.
Table of Contents
What WTRX does, and why the distinction matters
The SUN documentation on native TRX explains that SunSwap V2 and V3 required TRX to be wrapped into WTRX, while V4 supports native TRX. This is context for understanding different records, not a claim that every application requires wrapping.
The Universal Router documentation also describes native TRX wrapping and unwrapping via WTRX. The word “wrapped” here does not identify a transaction on Ethereum or a transfer to another blockchain.
For the broader explorer workflow, use our TRONSCAN beginner guide. This page handles the narrower task of identifying the wrapped asset and reconciling a deposit amount with an event. It does not replace a general address or transaction search guide.
Identify the WTRX contract before trusting a symbol
The checked Mainnet contract is TNUC9Qb1rRpS5CbWLmNMxXBjyFoydXjWFR. The SUN project’s backend API instructions, posted in May 2024, identify this address as Wrapped TRX with symbol WTRX and six decimals in their pair example.
On 30 October 2026 we opened the corresponding TRONSCAN token page and checked the full contract, TRC20 type and six-decimal precision. A symbol by itself is insufficient: a different contract can display similar branding.
| Asset | How to identify it in this task | What not to assume |
|---|---|---|
| Native TRX | Native transfer or contract-call amount, denominated in TRX/SUN | A token-list balance is native TRX |
| WTRX | Exact Mainnet TRC20 contract above; six decimals | Any token named Wrapped TRX is the same asset |
| USDT on TRON | Its own token contract and issuer context | Sharing a blockchain makes USDT and WTRX interchangeable |
If a WTRX amount appears in an old USDJ-related service record, use the USDJ sunset evidence guide to distinguish the token record from dated conversion instructions. The linked source-path review was checked on November 2, 2026; it does not establish a personal quote or redemption eligibility.
A real WTRX deposit to inspect
We selected a visible Deposit row from the contract’s transaction list and opened this confirmed Mainnet receipt: ea4cfc36a7572487f498d21a65a065d5a860d759ec0d81f9564333ffc6dcfcfb.
The block is 87,553,857, timestamp 30 October 2026, 04:36:00 UTC. The overview reported successful execution, method deposit(), method ID d0e30db0, the WTRX contract as the called contract, and an amount of 1 TRX.
The transaction Owner Address was TR7jTmHkGE4LJDEGDoDhvFm5hB3AsavrxA. This is a public address used to reproduce the reading exercise. We do not identify its operator or infer why the transaction was made.
WTRX event worksheet: reconcile the fields
The receipt’s Event Logs view displayed exactly one log, decoded as Deposit(address dst, uint256 sad). The emitting contract matched the WTRX contract. The indexed destination matched the transaction owner above, and the decimal data value was sad : 1000000.
| Field checked | Observed value | Interpretation |
|---|---|---|
| Native call value | 1,000,000 SUN / 1 TRX | Native amount attached to deposit() |
| Event type | Deposit | The receipt’s actual decoded event |
| Event sad | 1,000,000 base units | 1 WTRX using six decimals |
| Event destination | Same address as the transaction owner | Destination recorded by this deposit event |
| Current token balance | Not measured in this exercise | A historical event cannot supply today’s balance |
We saved a separate public explorer transaction-detail response. Its call_value was 1,000,000 and method was deposit(), matching the overview. This is another representation from the same explorer provider, not verification by an independent node.
The arithmetic is straightforward but the units matter: 1,000,000 SUN is 1 native TRX; 1,000,000 token base units is 1 WTRX at six decimals. The equal formatted quantities in this deposit do not make the assets identical in every interface.
Why this deposit is not a normal token Transfer row
This sample had a Deposit event rather than a decoded Transfer event. Do not invent a missing Transfer log or treat the absence of a Transfer row as proof that deposit() failed. Start with the successful receipt, the called contract, attached native value and the actual event type.
Equally, a Deposit event alone is not an audit of all later movements, reserves, contract safety or current withdrawal availability. It establishes the observed event in this particular receipt. A reader investigating an ordinary WTRX transfer should inspect that transfer’s own record rather than reusing the fields from this deposit.
How to check WTRX without connecting a wallet
- Choose Mainnet and the exact contract. Compare the full address with the cited project source, not just the WTRX symbol.
- Open a particular transaction. Record its full hash, block timestamp, result and called contract.
- Identify the operation. In this sample, it was deposit() with a native amount of 1 TRX.
- Read the actual Event Logs entry. Confirm the emitting contract, Deposit destination and raw sad value.
- Apply the checked decimal precision. Keep SUN conversion separate from token-unit conversion even when both use six places here.
- State the limit of the result. The success standard is a reconciled historical record, not a successful wallet operation or a current balance audit.
If you need an available native balance, move to the TRON address balance guide. A WTRX token amount should not simply be pasted into a native fee budget. Application-specific wrapping, unwrapping and account requirements need their own current checks.
When a WTRX check does not match
Different contract: stop the comparison and identify that asset first. A name match is not a contract match. Different network: return to the receipt’s network before comparing addresses. Different event: read the fields for that operation rather than expecting every receipt to contain Deposit.
Missing current balance: inspect the address’s current token entry separately and retain its observation time. Exchange does not list WTRX: do not infer deposit support from a TRON address format. The receiving service must explicitly support the actual asset and route.
Five frequently asked questions
1. Is WTRX the same entry as native TRX?
No. WTRX is a token representation through a particular contract; native TRX is the network asset. Keep their explorer entries separate.
2. Is WTRX a dollar stablecoin like USDT?
No. Wrapped TRX refers to TRX, not a dollar token. Sharing the TRC20 standard does not make the two assets equivalent.
3. Did the sample deposit show a token Transfer log?
No. Its one decoded log was Deposit. The native call value and that event were the appropriate fields for this reading exercise.
4. Does the sample prove today’s WTRX balance?
No. It is a historical receipt. Later movements and a separate current balance read could change the address’s holdings.
5. Must I connect a wallet to inspect WTRX?
No. We read the public token, contract and transaction pages without connecting or signing. Viewing records does not require a wrapping operation.
Sources, method and corrections
The independent Tronscan News editorial team checked the cited project documentation and public Mainnet record on 30 October 2026. The asset table, event worksheet, diagrams and eight field checks are original. AI assisted drafting and diagram preparation. We did not wrap, unwrap, approve, connect a wallet or send a transaction. Editorial standards and correction information are available from the Tronscan News homepage.
Leave a Reply