Three ways to write the same TRON address
| Format | Example | Used in |
|---|---|---|
| Base58 | TMVQGm1qAQYVdetCeGRRkTWYYrLXuHK2HC | wallets, exchanges, explorers |
| Hex | 417e5f4552091a69125d5dfcb7b8c2659029395bdf | TRON node APIs, smart contracts |
| EVM-style | 0x7e5f4552091a69125d5dfcb7b8c2659029395bdf | tools that expect 20-byte 0x addresses |
All three encode the same 20-byte account identifier. Base58 adds the 0x41 version byte and a 4-byte checksum; hex shows the version byte as 41; the EVM form drops it.
How to convert
- Base58 → hex: decode base58, verify the checksum, drop the last 4 bytes. The result starts with
41. - Hex → base58: take the 21 bytes (
41+ 20 bytes), append the first 4 bytes of SHA-256(SHA-256(data)) and encode in base58.
This page does both instantly and checks the checksum, so a mistyped address is rejected. Read more in TRON address format explained.
Important
The EVM 0x… form is shown for developers. Never send funds to it on another network such as Ethereum or BNB Chain — even though the bytes are the same, it is a different blockchain.
FAQ
Why does my TRON address start with 41 in the API?
Node APIs often return the hex form: 41 is TRON's version byte, followed by the 20-byte account identifier.
Is the converter safe to use?
Yes. It works offline in your browser and only handles public addresses — never paste a private key into any website.
Can I convert an Ethereum address to TRON?
Technically the 20 bytes can be wrapped in TRON's format, but that does not move any funds or create access. Only the holder of the private key controls either account.