BSV
BSV Intel
Network Intelligence Report
Sunday, March 15, 2026
Chain healthy · No reorgs detected
Blocks 940,349940,493 · 21,427 txs scanned
Block Interval
10.1m
Normal PoW cadence
Avg Txs / Block
150
143 blocks scanned
Mempool
165
1427.9 MB pending
Max Txs/Block
1,301
Peak activity
Connected Nodes
14
43% on Bitcoin SV:1.2.0
Capital Flow Monitor
144 movements
Major
9
>10K BSV · ~$149,350+
Notable
37
1K–10K · ~$14,935–149,350
Significant
98
100–1K · ~$1,494–14,935
Amount TX Shape Pattern
40,000.00 BSV
≈ $597,400
2d43520cc0... 1 4 neutral
25,813.91 BSV
≈ $385,531
166c8f800e... 1 3 neutral
25,759.54 BSV
≈ $384,719
a212178119... 1 5 distribution
25,062.16 BSV
≈ $374,303
b928c3f3eb... 1 2 neutral
24,870.23 BSV
≈ $371,437
f95965e8f2... 1 2 neutral
Chain Health
All Clear
Chain Tip
Single active tip
159 stale tips (normal PoW behavior).
Block Production
10.1 min avg
145-block span (24.3h). 61 fast blocks.
Transaction Volume
150 avg/block
21,427 total txs across 143 blocks. Peak: 1,301 txs.
Majority Client
Bitcoin SV:1.2.0
43% of 14 nodes. No version fragmentation.
Mining Distribution (143 blocks, full 24h)
CUVVE
25.2%
36 blks
taal.com
19.6%
28 blks
molepool.com
11.9%
17 blks
qdlnk
10.5%
15 blks
SA100
9.1%
13 blks
GorillaPool
7.7%
11 blks
taal.com_Teranode
6.3%
9 blks
Mining-Dutch
6.3%
9 blks
/rWGFYS/
3.5%
5 blks
Block Timing Analysis
145 blocks
Average Interval
10.1 min
Expected: ~10 min. Median: 6.3 min.
Range
0.1m – 46.4m
Fastest to slowest block interval observed.
Fast Blocks (<5 min)
61
Hashrate bursts or luck variance.
Slow Blocks (>20 min)
17
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.

Script Usage Taxonomy
89,395 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.
Purpose Distribution
77.9%
15%
7%
Payment Data Publication Contracts
PAYMENT
P2PKH69,659
P2PK0
Multisig10
DATA PUBLICATION
OP_RETURN10,809
Ordinal envelopes2,559
Spendable metadata*57
CONTRACTS
Custom locking scripts6,301
8 unique structures
Detected Protocols (from Data Publication)
MAP: 5
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.
TX fe41a99847... · Block 940,350 · 76 bytes
0
OP_0 <DATA>
Selected from 10809 candidates in this category.
* 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.
AI Network Analysis
Gemini Pro
BSV Network Health Report
Chain Status

Chain convergence normal. No deep reorg activity observed. Block production consistent with expected PoW cadence. The average block interval over the 24-hour window was 10.1 minutes. The network produced 61 blocks faster than 5 minutes and 17 blocks slower than 20 minutes, indicating typical variance in Proof-of-Work discovery times.

Economic Activity

A total of 21,427 transactions were processed across 143 blocks. Block content varied, with an average of 150 transactions per block, a maximum of 1,301, and a minimum of 1. A real-time mempool snapshot shows 165 pending transactions, occupying approximately 1.4 GB. This indicates moderate demand for block space, which remains well within the network's current capacity.

Mining Distribution

The mining distribution over the past 24 hours remains decentralized, with no single entity controlling a majority of the hashrate. Full 24-hour coinbase data shows the following distribution across 143 blocks:

CUVVE: 36 blocks (25.2%)

taal.com: 28 blocks (19.6%)

molepool.com: 17 blocks (11.9%)

qdlnk: 15 blocks (10.5%)

SA100: 13 blocks (9.1%)

GorillaPool: 11 blocks (7.7%)

taal.com_Teranode: 9 blocks (6.3%)

Mining-Dutch: 9 blocks (6.3%)

/rWGFYS/: 5 blocks (3.5%)

Whale Activity

Significant value was transferred on-chain, with 144 transactions exceeding 100 BSV. The activity was tiered as follows:

Over 10,000 BSV: 9 transactions

1,000 - 10,000 BSV: 37 transactions

100 - 1,000 BSV: 98 transactions

The largest movements included transactions of 40,000 BSV, 25,813 BSV, and 25,759 BSV. The observed patterns were primarily neutral (1-input to multiple outputs, likely including a change address) or simple distribution, suggesting coin management, internal transfers, or OTC desk activity rather than direct exchange inflows or outflows.

Script Taxonomy

Analysis of 89,395 transaction outputs reveals a clear hierarchy of use cases, dominated by standard value transfer.

Purpose: PAYMENT (77.9%), DATA_PUBLICATION (15%), and CONTRACTS (7%).

Structure: The most common script structures were P2PKH (69,659), OP_RETURN (10,809), Ordinal inscriptions (2,559), and stateful contracts (6,301).

Protocols: The MAP protocol was detected in 5 transactions.

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.

Example TX: [fe41a9984726...](https://whatsonchain.com/tx/fe41a998472619a0b25528b5ca7938cb0feb84d09806b36dfc5706ff413e0c23) at block [940,350](https://whatsonchain.com/block/940350)

Node Software

The network's node software distribution is currently split between two primary versions, indicating a need for continued monitoring for consensus alignment. The distribution across 14 connected nodes is:

/Bitcoin SV:1.2.0/: 6 nodes (43%)

/Bitcoin SV:1.1.0/: 6 nodes (43%)

/Bitcoin SV:1.1.1/: 2 nodes (14%)

*

Network stable with moderate economic activity.

Node Software Distribution
14 peers
Bitcoin SV:1.2.0 6 nodes 43%
Bitcoin SV:1.1.0 6 nodes 43%
Bitcoin SV:1.1.1 2 nodes 14%