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)
2,755,154 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-25 12:51 → 2026-04-26 10:26 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
5,628,520 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.
Structure (HOW data gets on chain)
51.1%
48.9%
0%
PaymentData PublicationContracts
PAYMENT
P2PKH195,479
P2PK2,680,492
Multisig6
DATA PUBLICATION
OP_RETURN2,751,636
Ordinal envelopes51
↳ BSV-20 tokens0
↳ BSV-21 tokens12
↳ NFT/media39
Spendable metadata*24
CONTRACTS / TOKENS
STAS tokens (Gen 2)0
STAS tokens (Gen 3)193
Custom locking scripts639
7 unique structures†
Protocols (Open standards for data format)
MAP: 1,255B://: 865OPUB: 474Metanet: 416AIP: 343
Metanet here refers to the 2018–2019 nChain protocol (4-byte "meta" push in OP_RETURN defining a DAG of parent-txid-linked records). Not to be confused with the newer BRC-100 "Metanet" wallet/overlay ecosystem, which uses the same word for a different thing.
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 embeds data inside a conditional branch. The OP_FALSE OP_IF block carries the payload (marked "ord"), while the P2PKH suffix enforces signature-based ownership.
Why it matters: Encodes ownership into individual satoshis. Transferable by spending the UTXO.
*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).