SegWit P2WPKH Output CountTRINITY EXCLUSIVE

EXCLUSIVE - Daily average count of P2WPKH (native SegWit) outputs created per block, from real full node script type indexing. Direct measure of native SegWit usage on-chain.

Tier performanceOn-chain Bitcoinprivacysegwitbech32p2wpkhexclusive

Trinity exclusive model

This metric is a proprietary Trinity Insights model. Its formula, inputs, weights and parameters are NOT disclosed. The page documents only the output (bounded scale, interpretation zones, historical context). Access to the score and its time series is via the REST API and the MCP server, subject to the required tier.

What is it?

This metric counts the number of P2WPKH (Pay-to-Witness-Public-Key-Hash) outputs created per block, then computes the daily average. P2WPKH is the native SegWit format for simple payments (addresses starting with bc1q), introduced by the SegWit soft-fork (BIP 141, August 2017). Unlike an adoption percentage, this direct output count reflects the actual volume of UTXO creation in native SegWit format. Each P2WPKH output represents a new UTXO assigned to a native SegWit address. Data is extracted directly from the full node Bitcoin.

How to read

The chart displays the average number of P2WPKH outputs per block for each day. The upward trend since 2017 reflects the ecosystem's gradual migration to native SegWit format. Peaks correspond to high transaction activity periods (bull runs, inscriptions). Troughs reflect calm network periods. In the post-mainstream-adoption era (2020+), the count oscillates structurally in the hundreds of outputs per block range, confirming P2WPKH has become the network's dominant format.

Key zones

Historical values range from 0 (before SegWit activation in August 2017) to peaks beyond 2,000 outputs/block during high-activity phases. In the post-adoption structural regime, P2WPKH remains the network's most-used script type. Above 1,500, the network is in high activity. Below 500, transaction activity is low or users have migrated to newer formats (P2TR).

What to observe

The relative trend between P2WPKH and P2TR is essential. If P2WPKH count declines while P2TR rises, it marks migration to Taproot - a network modernisation sign. If both rise simultaneously, it indicates growing overall activity. A prolonged P2WPKH plateau at high levels confirms native SegWit has become the ecosystem's de facto standard.

Historical context

SegWit was proposed by Pieter Wuille (December 2015) and activated on August 24, 2017, following the Blocksize War. Initial P2WPKH adoption was slow - Coinbase only migrated in February 2018. Economic pressure (reduced fees via the 75% witness discount) gradually pushed wallets and exchanges to adopt the native bech32 format (bc1q). Since 2022, P2WPKH largely dominates the network with over 1,000 outputs/block on average, confirming the SegWit transition's success.

Expert notes

⚠️ Trinity Exclusive Model - This metric counts outputs (not inputs). A P2WPKH output is identifiable by its 22-byte scriptPubKey (OP_0 <20-byte-hash>). Per-block counting then daily averaging smooths inter-block variations. P2WPKH does not cover complex SegWit scripts (P2WSH) or wrapped SegWit (P2SH-P2WPKH) - it is specifically the native format for single-key payments. Trinity separates each script type (P2PKH, P2SH, P2WPKH, P2WSH, P2TR) for maximum granularity. The impact on effective network capacity is non-linear: P2WPKH transactions are ~37% lighter than equivalent P2PKH transactions.

Common mistakes to avoid

Confusing the P2WPKH output count with a 'SegWit adoption rate' percentage is incorrect - this metric is an absolute count, not a ratio. A declining P2WPKH count does not necessarily mean SegWit regression: users may be migrating to P2TR (Taproot), which is also a SegWit format (bech32m). Similarly, a high count does not mean 100% of the network uses SegWit - legacy transactions (P2PKH) still coexist.

Programmatic access

REST API

curl -sS \
  'https://api.trinityinsights.io/api/v1/onchain/segwit-adoption-rate/history?days=90' \
  -H 'X-API-Key: $TRINITY_API_KEY'

MCP server

{
  "tool": "get_chart_value",
  "metric_id": "segwit-adoption-rate",
  "timeframe": "1y"
}

Required tier: performance. See the pricing grid for the tier list and the MCP documentation for multi-client configuration.

Related metrics

Institutional disclaimer

Trinity Insights is an educational and analytical tool. The metric above does not constitute investment advice. Trinity Insights is not a Crypto-Asset Service Provider (CASP) registered under MiCA Regulation (EU) 2023/1114. See the full disclaimer.