546,706 total txs across 144 blocks. Peak: 25,543 txs.
Majority Client
Bitcoin SV 1.2.0
68% of 19 nodes. 3 versions active.
Mining Distribution (144 blocks, full 24h)
taal.com
23.6%
34 blks
qdlnk
16.7%
24 blks
CUVVE
15.3%
22 blks
GorillaPool
14.6%
21 blks
SA100
9.7%
14 blks
molepool.com
8.3%
12 blks
/rWGFYS/
5.6%
8 blks
Mining-Dutch
4.9%
7 blks
unknown
1.4%
2 blks
◷ Block Timing Analysis
145 blocks
Average Interval
9.6 min
Expected: ~10 min. Median: 7.2 min.
Range
0m – 59.7m
Fastest to slowest block interval observed.
Fast Blocks (<5 min)
55
Hashrate bursts or luck variance.
Slow Blocks (>20 min)
18
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
546,706 txs mapped
Transaction volume by UTC hour, broken into 10-minute windows.
Coverage: 2026-03-19 14:34 → 2026-03-20 13:21 UTC
Peak: 25,730 txs/windowCoverage: 145 blocks
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
1,099,152 outputs
This section describes how Bitcoin scripts were used in this scan window.
We classify activity in three layers: purpose, structure, and protocol.
Purpose describes why an output exists (payment, data publication, or programmable conditions).
Structure describes how that purpose is implemented in script (e.g., P2PKH, OP_RETURN, conditional envelope).
Protocol describes the semantic meaning of embedded data when identifiable (e.g., MAP, B://).
Because Bitcoin Script does not explicitly declare intent, some classifications are inferred from structure and are labeled as heuristic where appropriate.
Protocol detection is based on known marker patterns. Absence of a marker does not imply absence of meaning.
⬡ Script of the Day — Data Carrier (OP_RETURN)
What it does: This script begins with OP_RETURN, which terminates execution and marks the output as unspendable. The remaining bytes carry arbitrary data.
Why it matters: Currently the most common method for data publication. Used by protocols like B://, MAP, AIP, and TreeChat for files, metadata, and social content.
*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.