Tron Address Converter – Base58 (T…) to Hex (41…) and 0x Format

What is a Tron address converter?

A Tron address converter translates one 20-byte account between its three spellings: the Base58Check T… form shown by wallets (prefix byte 0x41, then 20 bytes, then a 4-byte double-SHA-256 checksum), the 42-character 41… hex form used by node APIs and raw transactions, and the 0x… form used by EVM tooling. All three refer to the same account.

The three forms, explained

Base58 (T…): 34 characters, always starts with T on mainnet. This is what TronLink, Trust Wallet, Binance and OKX show and accept. It contains a 4-byte double-SHA-256 checksum.
Hex (41…): 42 hex characters: the version byte 0x41 followed by the 20-byte account. Used in TronGrid REST responses, tronweb internals and raw transactions.
EVM-style (0x…): the same 20 bytes with a 0x prefix, as seen in TVM contract logs and Solidity tooling. Shown here in EIP-55 checksummed and lowercase variants.

How the conversion works

Base58 → hex: decode Base58, strip the last 4 checksum bytes after verifying them, output the remaining 21 bytes as hex.
Hex → Base58: take 41 + 40 hex, append the first 4 bytes of SHA-256(SHA-256(bytes)), encode in Base58.
0x → Tron: prepend 41 to the 40 hex characters and encode as above.

Worked example

The USDT TRC-20 contract is TR7NHqjeKQxGTCi8q8ZY4pL8otSzgjLj6t in Base58. Decoding gives the 21-byte payload 41a614f803b6fd780986a42c78ec9c7f77e6ded13c plus 4 checksum bytes. Dropping the 41 prefix and adding 0x yields the EVM form 0xa614f803b6fd780986a42c78ec9c7f77e6ded13c, which is how the same contract appears in TVM event logs.

Formats at a glance

Form	Length	Checksum	Where used
Base58 T…	34 characters	yes, 4 bytes	wallets, exchanges, QR codes
Hex 41…	42 hex characters (21 bytes)	no	TronGrid, tronWeb, protobuf transactions
EVM 0x…	42 characters (20 bytes)	optional EIP-55 case	TVM logs, Solidity tooling

Typical uses

Querying /v1/accounts/<hex> style API endpoints that only accept hex.
Decoding the to parameter of a TRC-20 transfer call from contract data.
Checking that a deposit address a customer sent is a valid Tron address before you credit a withdrawal.

Generate a receiving code for a verified address with the USDT TRC-20 QR generator.

Frequently asked questions

Why does Tron have three address formats?

Internally a Tron account is 20 bytes, like an Ethereum account. Wallets show it as Base58Check with a 0x41 version byte, which produces the familiar T… string with a checksum. Node APIs and the TVM work with the raw hex, 41 followed by 40 hex characters. Because the TVM is EVM-compatible, the same 20 bytes can also be written as a 0x address.

Can I send USDT TRC-20 to the hex form?

No. Wallets and exchanges only accept the Base58 T… form for deposits. The hex and 0x forms are for developers. Convert to T… before sharing.

Is a Tron address the same as an Ethereum address?

They share the 20-byte format, and a private key would produce both, but they are different networks. Sending ERC-20 USDT to a T… address is impossible, and sending TRC-20 USDT to the 0x form of your Ethereum address does not land in your Ethereum wallet.

What does checksum failed mean?

The T… address did not pass Base58Check verification: one or more characters are wrong. Do not use it.

Why does a Tron address always start with T?

Because Base58Check encoding of a 25-byte payload whose first byte is 0x41 always begins with the character T on mainnet. The prefix is a property of the version byte, not something a user chooses.

Does the converter validate the address?

Yes. The Base58 form is checksum-verified before conversion, and hex input must be exactly 42 characters beginning with 41 or a 40-hex 0x address.