UTXO Set

Overview

Each UTXO is identified by a transaction ID and output index and includes value plus the condition required to spend it. When a node receives a transaction, it checks that every referenced input exists in the current set, has not already been spent, and can be unlocked by the supplied authorization.

After a valid block is accepted, nodes remove consumed outputs and add newly created outputs. Coinbase outputs may enter the set with maturity restrictions. Reorganizations require reversing the old branch’s changes and applying the replacement branch.

The size and structure of the UTXO set affect node performance. Millions of small outputs increase database storage, random-read demand, snapshot size, and synchronization cost. This is why dust and output-creation policies matter beyond individual wallets.

Nodes can accelerate startup by loading a verified UTXO snapshot and then validating newer blocks. The snapshot must correspond to a trusted block commitment or checkpoint. A corrupted or mismatched set can cause invalid transaction acceptance or rejection.

Applications should distinguish the UTXO set from total transaction history. Spent outputs remain visible historically but are absent from active spendable state. A wallet balance is derived from the subset of the UTXO set controlled by its keys and policies.

The set can be committed through snapshots or accumulator-style structures, but every implementation must use deterministic serialization and update rules. Operators should monitor set size, database latency, and cache performance. A node that is fully synchronized in block height can still serve incorrect results if its UTXO database is corrupted, so periodic integrity checks and verified recovery paths are important.