Like most Cosmos SDK chains, Gonka stores and transmits token amounts on chain as integers in a micro-denomination — a "u"-prefixed unit worth a small fraction of one whole token — rather than as decimal GNK. This is why raw amounts and fee fields in transaction data look like large integers rather than numbers with decimal points: the chain is counting micro-units, and the explorer's job is to convert that back into a human-readable GNK figure before displaying it.

This matters most where the chain's accounting is visible but the fee itself is zero: ordinary Gonka transactions carry no gas charge (the network's entire fee model lives in inference pricing instead), but gas accounting — used and wanted — is still recorded on every transaction and block, denominated in the same base units the chain uses internally.

Because inference fees, escrow amounts, work-coin payouts, and reward-coin mints are all GNK-denominated values moving through the same accounting system, they are likewise expressed in base units on chain before GNKScan renders them as GNK. If you're inspecting raw transaction or address data and see an amount that looks too large by a factor of a million (or a billion, depending on the exact scale factor in use), it's very likely a base-unit figure rather than a display error.

For the fee model these amounts flow through — escrow, work coins, reward coins, vesting — see Gonka Tokenomics: How GNK Fees and Rewards Work.