Skip to content

← On-chain Bitcoin

Taproot Output Count (P2TR)TRINITY EXCLUSIVE

EXCLUSIVE - Daily average count of P2TR (Taproot) outputs per block, from real full node script type indexing. Direct measure of Taproot adoption velocity - how many outputs are being created using Bitcoin's latest script type.

Tier performanceOn-chain Bitcoinprivacytaprootp2trschnorradoptionexclusive

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 P2TR (Pay-to-Taproot) outputs created per block, then computes the daily average. P2TR is the script type introduced by the Taproot soft-fork (BIP 340/341/342), activated at block 709,632 (November 14, 2021). Taproot combines Schnorr signatures, MAST (Merkelized Abstract Syntax Trees), and an improved scripting system. On the privacy side, key path spends make simple payments, multi-sig, and complex contracts indistinguishable on-chain. The metric measures the absolute volume of P2TR UTXO creation - a direct indicator of Taproot activity on the network, computed from the full node Bitcoin.

How to read

The chart displays the average number of P2TR outputs created per block each day. Values were 0 before the November 2021 activation, then rose gradually. Marked peaks correspond to Ordinals/Inscriptions activity waves (which heavily use P2TR). The underlying trend, excluding Ordinals peaks, reflects real adoption for payments and Lightning Network - in the post-activation era it oscillates structurally below a few hundred outputs per block for organic usage.

Key zones

Historical values range from 0 (before November 2021) to peaks beyond 2,500 outputs/block during Ordinals activity waves. Above 500 outputs/block, Taproot activity is high (often driven by inscriptions). Below 100, it represents the baseline level of standard Taproot payments. The organic regime excluding Ordinals remains structurally modest compared to P2WPKH, reflecting the still-early stage of wallet/exchange adoption.

What to observe

Comparison with the P2WPKH count (which largely dominates the network by more than an order of magnitude) puts Taproot adoption in perspective: P2TR still represents a fraction of native SegWit volume. The relative trend is key - if P2TR grows while P2WPKH stagnates or declines, it marks migration to the most modern format. Ordinals peaks temporarily inflate the count, but the underlying trend excluding inscriptions is the true maturity indicator. Adoption by major exchanges for withdrawals marks scaling for daily use.

Historical context

Taproot was proposed by Gregory Maxwell (January 2018) and integrated into Bitcoin Core by Pieter Wuille (BIP 340-342). The soft-fork activated via the Speedy Trial mechanism. Unlike SegWit, activation did not generate major controversy. Initial adoption was nonetheless even slower than SegWit's, as wallets had no immediate economic pressure to migrate. The unexpected catalyst was Ordinals/BRC-20 in early 2023, which sent P2TR counts from ~50 to over 2,000 outputs/block. Since then, the baseline has structurally increased, a sign that organic adoption benefited from Ordinals exposure.

Expert notes

⚠️ Trinity Exclusive Model - A P2TR output is identifiable by its 34-byte scriptPubKey (OP_1 <32-byte-key>). Per-block counting then daily averaging smooths inter-block variations. Taproot has deep privacy implications: key path spends reveal only a Schnorr signature and an x-only public key - impossible to distinguish a simple payment from a 3-of-5 multisig or Lightning HTLC. Script path spends reveal only the executed script (not unused branches) thanks to MAST. The P2TR count is a direct proxy for Schnorr adoption, a prerequisite for MuSig2 and FROST.

Common mistakes to avoid

Confusing the absolute P2TR output count with an adoption percentage is incorrect - this metric is a count, not a ratio. A modest organic count may seem 'low' compared to P2WPKH, but Taproot (activated November 2021) is much more recent than native SegWit (activated August 2017), and wallet/exchange adoption follows longer development cycles. Similarly, Ordinals-related peaks do not reflect payment adoption: one must distinguish the baseline count (payments, Lightning) from the total count (including inscriptions) to evaluate true adoption.

Programmatic access

REST API

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

MCP server

{
  "tool": "get_chart_value",
  "metric_id": "taproot-adoption",
  "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.