1,258,000 total txs across 143 blocks. Peak: 63,823 txs.
Majority Client
Bitcoin SV:1.2.1
52% of 21 nodes. 4 client versions observed.
Mining Distribution (143 blocks, full 24h)
taal.com
22.4%
32 blks
CUVVE
21%
30 blks
Mining-Dutch
13.3%
19 blks
SA100
12.6%
18 blks
qdlnk
12.6%
18 blks
GorillaPool
9.8%
14 blks
unknown
4.9%
7 blks
molepool.com
3.5%
5 blks
◷ Block Timing Analysis
144 blocks
Average Interval
10.4 min
Expected: ~10 min. Median: 7.6 min.
Range
0.1m – 61.6m
Fastest to slowest block interval observed.
Fast Blocks (<5 min)
51
Hashrate bursts or luck variance.
Slow Blocks (>20 min)
21
PoW variance — expected in Poisson process.
A Poisson process is a random event process where events occur independently at a stable average rate, but with unpredictable spacing.
▦ Transaction Velocity (10-min intervals, not per-block)
1,258,000 txs mapped
Transaction volume shown chronologically. Each row = one hour of the scan, each column = a 10-minute window. Read top-to-bottom for earlier-to-later.
Coverage: 2026-04-06 09:53 → 2026-04-07 10:29 UTC
Dark cells indicate 10-minute windows where no block was mined — a natural result of the Poisson process governing Proof of Work. Transactions during these windows appear in the next mined block.
⬡ Script Usage Taxonomy
2,680,888 outputs
This section describes how Bitcoin scripts were used in this scan window.
We analyze outputs across three orthogonal dimensions:
Structure: HOW data gets on chain (OP_RETURN, Ordinal envelope, Spendable metadata, STAS, P2PKH)
Protocol: Open standards defining data format (B://, MAP, BSV-20/21, Metanet)
Content Type: MIME types from inscriptions (text/plain, image/png, application/json)
OP_RETURN data is prunable at scale (requires indexing). STAS and Spendable metadata remain in the UTXO set.
Identifiable patterns in data transactions. Most chain activity has no such identifier.
Some patterns from WoC tags, others identified through analysis.
Note: WoC's taxonomy mixes protocols, apps, and content types. It's also limited to OP_RETURN patterns, which are prunable and represent just one way to embed data on chain.
What it does: This script uses conditional logic (OP_IF/OP_ELSE), byte manipulation (OP_SPLIT/OP_CAT), or hash operations to enforce spending conditions beyond simple signature verification.
Why it matters: Demonstrates BSV's full scripting capability for programmable money and stateful applications.
*Spendable metadata (heuristic): Scripts with signature verification followed by data removed via OP_DROP. Metadata not consumed by validation logic but remains on-chain.
†Unique structures: A contract structure is a normalized script skeleton with variable data (hashes, signatures, pubkeys) removed.
‡Content Types: MIME types declared in inscription data. application/bsv-20 is the MIME type for BSV-20 fungible token inscriptions (also counted in the ordinal breakdown above).