When moving from a centralised exchange to a wallet, check a token’s decimal setting before judging its displayed balance or approving a swap. An exchange may show a neat decimal amount while handling the underlying units for you; in a self-custody wallet, the displayed amount is still a human-readable version of an integer recorded on-chain.
Imagine you hold 12.345678 USDT in TronLink and want to exchange some of it. The six digits after the decimal point are not decoration: they show the smallest fraction this TRC-20 token can represent. Knowing how that display maps to the contract’s units helps you spot precision limits and understand what a quoted swap amount means.
What do token decimals tell you?
Decimals specify how many places a token uses to display its smallest on-chain units. With six decimals, one whole token equals 1,000,000 base units, so 12.345678 USDT is represented by the integer 12,345,678. The contract works with that integer; the wallet divides by 1,000,000 to show the familiar amount.
TRX uses a related unit system: one TRX equals 1,000,000 sun. TRC-20 tokens set their own decimal count in their contract, commonly six or eighteen, so do not assume every token follows USDT’s format. The contract’s decimal value determines how raw units become a displayed balance.
This is a precision rule, not a price rule. Six decimals do not mean a token is worth less than one with eighteen, and changing the display precision does not change a token’s market value. It sets the smallest representable increment: with six decimals, an amount cannot be represented more precisely than 0.000001 token.
Why can a wallet amount differ from an exchange amount?
The numbers can look different because platforms format, round, or hide trailing zeroes differently. A wallet might show 12.3456 where another interface shows 12.345600; those are the same amount if both refer to the same token contract. A more consequential mismatch is reading a token with six decimals as though it had eighteen: the raw integer would translate to a balance off by a factor of a trillion.
Before comparing balances, check the token’s network, contract identity, and decimal count. The ticker alone is not enough: different contracts can use the same symbol, and a lookalike token may display a familiar name. For a TRON swap, the selected asset’s contract and decimals determine how the entered amount is converted into the integer sent to the smart contract.
If you need the full explanation of the wallet-based exchange itself, read how a TRON swap exchanges tokens. Here, the key point is that the amount you enter is a readable representation; the transaction uses the token’s base units. That conversion happens before the swap contract can act on the amount.
How do decimals affect a swap quote?
Decimals affect the amount that can be entered and encoded, while the quote reflects the exchange rate, pool conditions, and any applicable swap settings. Suppose a quote estimates 2.5 TRX for 4.123456 USDT. The USDT side is encoded as 4,123,456 base units; the TRX side uses sun, so 2.5 TRX corresponds to 2,500,000 sun.
A quote may show fewer decimal places than the token supports. That can be a display choice or a limit in how the swap handles output precision; it does not automatically mean the token contract has fewer decimals. Look at the smallest quoted or receivable increment. If the amount rounds down, the actual output can be slightly below the unrounded estimate.
Decimals do not set network transaction costs. TRON resources such as Energy and Bandwidth, along with the swap’s own pricing and execution conditions, are separate from the token’s display precision. A tiny amount can still require a transaction, and a token supporting many decimal places does not make the transaction cheaper.
What should you check before confirming?
Use the selected token’s displayed balance and confirm the token identity before entering an amount. Check that the input fits the token’s precision, then compare the quoted output at the precision actually shown. If a service asks for more digits than the token supports, or the displayed balance seems implausibly large or small, stop and verify the contract details instead of guessing where the decimal point belongs.
After submission, inspect the transaction record in a TRON explorer if you need to reconcile the amount. A TRC-20 transfer record may show a raw integer alongside the token’s decimal count; divide by 10 raised to that count to recover the human-readable amount. For example, 4,123,456 with six decimals is 4.123456 tokens. That check connects the wallet display to what the contract processed.
Can I send or swap a fraction smaller than the last displayed digit?
No. A token with six decimals cannot represent increments smaller than 0.000001 token, even if an interface lets you type more digits. The amount must ultimately convert to an integer number of base units, so excess precision may be rejected or rounded by the software. Check the resulting quote before confirming.
Do all TRC-20 tokens use six decimals?
No. The token contract defines its decimal count, and TRC-20 assets can use different values. USDT on TRON uses six decimals, but another token may use a different precision. Verify the selected contract’s metadata instead of copying a decimal assumption from another asset, even when their symbols look similar.