Spent Output Script Type Distribution
- 1M1M
- 3M3M
- 6M6M
- 1Y1Y
- ALLALL
About this metric
What it measures
Spent Output Script Type Distribution groups the outputs spent each day by their locking-script type and shows each group's share of the spent-output count, in percent. It separates P2PK, P2PKH, Bare multisig, P2SH (non-SegWit), P2SH-P2WPKH, P2SH-P2WSH, P2WPKH, P2WSH, P2TR (Taproot) and Non-standard.
How to read it
An expanding group means more of the day's spent inputs use that script format. P2PKH reached about 99.91% on March 4, 2014, while P2WPKH reached about 82.62% on June 20, 2026, providing reference points for the shift from legacy spending toward native witness formats.
The chart counts spent outputs, not BTC value, new addresses or the stock of unspent coins. A consolidation with many inputs can change the mix without many users changing wallets. Older formats may reappear when dormant coins move, and the earliest days have too little spending for their extreme shares to describe broad adoption.
- Frequency
- Daily (UTC 00:00)
- Asset
- BTC
- Category
- Transfers & Transactions
- Type
- Breakdown
- Data since
- 2009-01-03
- Latest data
- 2026-10-27
FAQ
Does this chart classify newly created outputs or spent ones?
It classifies the previous outputs consumed as inputs in the day's transactions. It therefore describes the formats coins are being spent from, rather than the formats receiving new coins.
Why is P2SH split into SegWit and non-SegWit categories?
P2SH can wrap different spending conditions. P2SH-P2WPKH and P2SH-P2WSH identify wrapped witness spending, while P2SH (non-SegWit) keeps other P2SH uses separate.
Is the P2TR share equal to Taproot transaction adoption?
It aligns with the input-level view, since it counts spent P2TR outputs. Taproot transaction adoption instead counts transactions containing at least one such input, so the percentages can differ.
