Five Decimal Checks for Cross-Chain Treasury Balances

To compare a treasury balance across chains, first check what unit each number uses. A token may be shown with a different number of decimal places in a wallet, a contract, or a report. That can make equal amounts look different, or make a real mismatch easy to miss.

Decimals set how a token’s smallest unit is counted. If a token uses 6 decimals, one whole token is represented in the contract as 1,000,000 base units. A display tool usually moves the decimal point for you. Treasury checks should still compare the raw amounts and the display rule behind them.

A bridge can add another step: tokens may be locked on one chain and represented by a separate token on another. For more on that flow, see this guide to what to know before moving tokens through the Polygon Bridge. The key is to check which token contract the balance belongs to.

How do you check a token’s decimals?

Check 1: Match the token contract. Start with the contract address on each chain, not just the ticker or token name. Different contracts can use the same symbol and have different decimal settings.

Check 2: Read the raw balance. Compare the balance in base units before converting it to a human-readable amount. For an 18-decimal token, divide the raw balance by 10¹⁸ to get whole tokens. Use the decimals reported by that specific contract; do not assume every token uses 18.

What should you compare across chains?

Check 3: Confirm the display conversion. Make sure both reports use the same decimal rule and rounding. A dashboard that rounds to two places can hide a small remainder, while a raw balance shows it. Keep the full precision for reconciliation.

Check 4: Match the bridge representation. Record whether each balance is the original token, a wrapped token, or another bridged representation. Add up only the balances that belong in the same treasury view. A token on the destination chain may represent an amount held or accounted for elsewhere.

For a quick review, keep these fields together for each balance:

• Chain and token contract address
• Raw balance and token decimals
• Displayed amount and rounding rule
• Bridge representation, if there is one

How do you spot a real balance mismatch?

Check 5: Reconcile timing and movement. Compare balances at the same point in time. A transfer can leave one chain before it appears on another, depending on the bridge process. Check transaction records and pending transfers before treating the gap as a loss.

Then convert each balance using its own contract’s decimals and compare like with like. If the displayed totals differ but the normalized amounts and bridge records agree, the issue may be presentation. If they still differ, trace the raw balance and transactions for the specific chain and contract. That is a clearer starting point than relying on a ticker or a rounded dashboard total.