Balance, nonce, code and storage commitments answer different questions.
LET’S PICTURE IT
A profile contains separate counters, funds and references to detailed records.
SEE IT FOR YOURSELF
Pack small values into Solidity storage slotsStep 1 / 4
In this simple default-layout example, two uint128 values come before one uint256. Each slot holds thirty-two bytes.
In this simple default-layout example, two uint128 values come before one uint256. Each slot holds thirty-two bytes.The first sixteen-byte value occupies the low-order half of slot zero. Low-order bytes are shown on the right.The second uint128 fits in the remaining sixteen bytes. Both values now share slot zero.C needs a complete thirty-two-byte slot, so it begins at slot one. Two packed small values plus C use two slots.
Animated local teaching model. No wallet, RPC or live blockchain data. Some labels and hashes are abbreviated for readability.
Read the balance in raw units
The execution account balance represents Wei under the relevant state. Token balances are normally tracked by token contracts rather than being separate native-balance fields here.
Separate nonce meaning
The account nonce participates in transaction and creation rules. It is not the number of every internal call or every token transfer involving that address.
Follow code and storage references
The account model contains a code hash and storage root. Those references are not the full source code or all storage values printed directly in the account record.
Bind the snapshot
An account record belongs to a state context. A proof at one block does not automatically establish the account’s values at a later block.
Map the protocol concept
account record concepts:
nonce
native balance
storage commitment
code commitment
A conceptual model. Exact fields, limits and processing rules must be checked against the intended network fork.
QUICK CHECK · NO PRESSURE
Are ERC-20 balances native account-balance fields?