What is this?

The UTXO Count chart tracks the total number of Unspent Transaction Outputs in the Kaspa network over time. UTXOs are the fundamental unit of value in Kaspa's (and Bitcoin's) accounting model — unlike account-based blockchains like Ethereum, Kaspa doesn't maintain balance records. Instead, your "balance" is the sum of all UTXOs your wallet controls. Each UTXO is a discrete, indivisible chunk of KAS that was created as the output of a previous transaction and has not yet been spent.

Think of UTXOs like individual bills in a physical wallet. If someone sends you 100 KAS in three separate transactions of 50, 30, and 20 KAS, your wallet holds three UTXOs. When you want to spend 75 KAS, your wallet selects UTXOs to cover that amount (e.g., the 50 + 30 UTXO), consumes them entirely, and creates new UTXOs: one for the 75 KAS payment and one for the 5 KAS change back to you.

The total UTXO count is therefore a direct measure of the network's state complexity — how many individual pieces of unspent value exist across all wallets. It reflects both the number of unique holders and the transaction patterns of existing users, making it a composite adoption and activity metric.

How to use this data

A rising UTXO count is a strong signal of network adoption and organic activity. Each new UTXO generally represents either a new holder receiving KAS for the first time, or an existing holder receiving a new payment. Sustained UTXO growth during price declines is particularly bullish — it suggests accumulation by new participants even as price action discourages speculation.

Conversely, a declining UTXO count indicates consolidation — users are combining multiple UTXOs into fewer, larger outputs. This can happen during wallet maintenance, exchange consolidations, or when large holders reorganize their funds. Temporary UTXO count drops are normal and healthy; sustained declines may indicate reduced network usage or a shrinking user base.

Compared to Bitcoin's UTXO set (approximately 170+ million), Kaspa's UTXO set is younger and smaller but growing rapidly. UTXO bloat — where the set grows so large it strains node resources — is a known scalability concern for UTXO-based chains. Kaspa addresses this through its pruning mechanism and UTXO commitment model, which allows nodes to verify the UTXO set integrity without storing the full transaction history. This makes Kaspa more sustainable at scale than naive UTXO implementations.

How it's computed

The UTXO count is obtained by querying the total number of entries in Kaspa's UTXO set, stored in our RocksDB secondary instance that mirrors the full node's state. This secondary instance allows us to perform heavy read queries without impacting the node's consensus performance. The count is sampled hourly to produce the historical time series.

Each sample captures the exact cardinality of the UTXO set at that point in time. New UTXOs are created whenever a transaction produces outputs, and UTXOs are destroyed (spent) whenever they are consumed as inputs to a new transaction. The net change per block depends on the transaction mix — a simple one-input, two-output transaction destroys one UTXO and creates two, resulting in a net increase of one.

Mining coinbase transactions always create new UTXOs without consuming any (since they have no inputs), so the UTXO count has a natural upward pressure from block rewards alone. The rate of this baseline growth depends on the number of miners and how block rewards are split across outputs. Understanding this baseline helps distinguish organic adoption growth from mechanical mining effects.