Account Model

In an account model, the ledger records state under accounts and transactions apply ordered changes to that state. A simple account may hold a balance and nonce; a contract account can also hold code and storage, depending on the network.

Sender nonces or equivalent ordering rules prevent replay and determine which state a transaction reads. Transactions touching the same accounts can conflict, while implementations may execute or validate independent state accesses in parallel when the protocol exposes enough information.

A UTXO model consumes discrete outputs and creates new ones instead of mutating one account balance. Account models can make persistent shared contract state direct to express; UTXOs can make ownership and transaction dependencies explicit. Privacy, parallelism, wallet complexity, and state growth depend on the full protocol and application design, not the ledger label alone.