Understand Token Decimals Before Reading a Raw Amount

A raw token amount is an integer counted in the token’s smallest units. Decimals tell an interface where to place the decimal point; the same raw integer can represent very different readable quantities for different assets.

Apply the scale to an illustrative token

Consider a hypothetical token with six decimals and a raw balance of 1234567. Dividing by 10 to the power of six gives 1.234567 tokens. With eighteen decimals, the same raw integer instead represents 0.000000000001234567 tokens. These are arithmetic examples, not balances or token recommendations. Always establish the contract and network before applying a decimal scale to a value copied from an explorer or response.

Verify the metadata instead of assuming a default

ERC-20 describes decimals as an optional method. A tool should not assume every token supplies it or that every token uses eighteen places. Use the authoritative asset reference and the verified contract’s readable information where available. If a tool cannot establish the scale, mark the interpretation uncertain. Guessing six places because a ticker looks like a familiar stablecoin can turn an identity problem into a misleading balance.

Distinguish rounding from the stored amount

Suppose a raw six-decimal value represents 1.234567 but a compact view shows 1.23. The shorter display alone does not establish that 0.004567 tokens were removed. Inspect the full quantity or raw value before drawing that conclusion. Conversely, copying 1.23 back into an input does not preserve all the original units. Keep the original full-precision value when comparing two observations of the same asset.

Use decimal knowledge without changing permissions

Checking an amount’s scale does not require an approval. In RunixCoin, the public WETH input accepts at most eighteen decimal places, while estimated USDC output is formatted with six; that describes the inspected interface and is not a rule for arbitrary tokens. A parsed amount also does not verify account holdings, network fees or execution. Resolve token identity and units before treating an estimate as meaningful, and do not use a signing request to test your arithmetic.

References and verification

Reviewed 10 November 2026. Product details reflect inspected interface code; camera scanning, browser behavior and mainnet execution were not verified.