A positive raw token balance can appear as zero if a wallet displays fewer decimal places than the token supports. Divide the integer balance by ten raised to the verified decimals value to calculate the human-readable quantity. Then check transfer costs and receiving minimums separately: a nonzero quantity is not automatically an economical or supported transfer.
Separate three numbers on the screen
The raw balance is an integer used by the token system. The token quantity is that integer expressed in the unit described by its decimals metadata. A fiat valuation is a further calculation using a price source. A wallet may truncate or round either of the last two displays. Therefore, a zero fiat value, a zero rounded quantity and a genuinely zero raw balance are different observations.
The OpenZeppelin ERC-20 explanation describes integer accounting and the display role of decimals. A standard implementation may have a familiar default, but that is not permission to assume the same value for every token. The ERC-20 specification treats decimals as optional metadata. An application has to handle the token it actually encounters, including missing or unusual metadata.
A decimal point does not belong inside the raw integer
Take a fictional token with six decimals. A raw balance of 1,234,567 represents 1.234567 tokens, because the integer is divided by 1,000,000. The commas here separate thousands in the integer; they are not decimal marks. Confusing a raw integer with an already formatted amount can make an ordinary balance look a million times larger or smaller than it is.
The token decimals converter can help check that arithmetic. Use the decimals value verified for the exact asset and network, not one copied from an unrelated token with the same ticker. Keep the original integer in your notes. Converting through a short rounded display and then trying to recover the original precision can lose the very information you were checking.
| Illustrative raw balance | Decimals | Token quantity | Possible two-decimal display | Interpretation |
|---|---|---|---|---|
| 1,000,000 | 6 | 1 | 1.00 | One whole token in the chosen unit |
| 1,234,567 | 6 | 1.234567 | 1.23 | The display omits smaller digits |
| 1 | 6 | 0.000001 | 0.00 | A positive smallest unit may be visually rounded away |
| 1,000,000 | 18 | 0.000000000001 | 0.00 | The same integer means a different quantity with another precision |
| 1,000,000,000,000,000,000 | 18 | 1 | 1.00 | Large raw integers do not necessarily mean many tokens |
This table uses fictional balances and an illustrative display restricted to two decimal places. It does not describe the rounding policy of a particular wallet. Some interfaces show extra digits for small amounts; others hide negligible values or omit a price entirely. Inspect the full quantity or verified raw balance instead of treating one presentation choice as a change to the ledger.
Verify precision for the specific contract or mint
Identify the network and the actual token contract before reading its metadata. A ticker is a name, not a unique cross-chain identifier. A wrapped or unrelated token can use a familiar name without sharing the original token's accounting. The existing native coin and token guide explains why a token balance also differs from the network asset used to pay for a transaction.
On Solana, the official mint-account guide describes decimals as part of the mint's configuration. Inspect the actual mint, rather than importing a precision value from an Ethereum contract or another Solana token. The fact that an interface recognizes a logo does not establish the asset's identity. Use the issuer's verified references and an appropriate explorer when reconciling a receiving payment.
If a token contract does not provide the expected metadata, do not fill the gap by assuming a convenient value. A wallet's fallback or custom-token setting can explain a display mismatch, but changing that local display does not mint coins or increase the raw balance. Document the source of any correction. When the metadata remains uncertain, describe the uncertainty instead of presenting an unverified amount as a confirmed payment.
Why a visible balance may still be unavailable to send
Precision answers how an amount is represented, not whether the transfer will be accepted. Your wallet may need a separate network asset, the token may impose restrictions, and the receiving platform may apply a minimum. None of those rules follows automatically from the number of decimals. Adding more decimal places to a display does not solve a missing signing key or a contract that refuses a transfer.
Likewise, a difference between the sent and received raw amount is not always a rounding issue. Confirm that you are comparing the same token, account, network and point in time. Then inspect the executed transfer and any applicable token behavior. A display conversion should explain the observed figures exactly; if it does not, continue the transaction investigation instead of forcing every shortfall into the decimals explanation.
Reconcile a small balance in this order
- Record the network, full token contract or mint, account and raw integer balance. Avoid using a fiat valuation as the original data.
- Verify the decimals metadata from the actual asset. Note whether the application obtained it directly or used a local override.
- Convert the integer once and retain the full result. Compare that with the wallet's displayed quantity and any rounding or hidden-balance settings.
- Check whether the proposed sending amount is representable in the token's smallest units. Do not append unsupported fractional digits.
- Only then inspect network costs, token restrictions and the receiver's current minimum. These determine whether a transfer is practical, separately from display precision.
A useful support report includes both representations and the metadata source: for example, the raw integer, decimals value, resulting token quantity and screenshot of the shorter display. Public identifiers are usually enough to describe this arithmetic. There is no reason to disclose a recovery phrase or sign a spending approval merely so someone can explain a decimal point.
For a no-account swap, compare the exact supported input amount with the current order rather than copying an ambiguous rounded portfolio figure. Inspect the service fee information and receiving conditions before deciding whether to move a tiny remainder. The mathematical existence of a smallest token unit does not promise that an order accepts that unit as its minimum.
FAQ
What do token decimals mean?
They specify how a raw integer is presented in human-readable token units. The conversion divides the integer by ten raised to that decimals value; it does not determine the token's market price.
Where do I find token decimals on Solana?
Check the configuration of the exact token mint using verified project references and an appropriate explorer. Do not reuse another mint's value merely because its ticker or logo looks similar.
How should I check USDC token decimals?
First identify the network and verify the particular USDC contract or mint against the issuer's references. Use that asset's metadata for the conversion rather than guessing from a different deployment or a similarly named token.