Embedded Data
OP_RETURN protocols, Ordinals inscriptions, protocol fee analysis, and miner coinbase messages
Analyze protocol data and inscription content embedded in Bitcoin transactions. OP_RETURN protocols like Runes, Omni Layer, and Counterparty use dedicated outputs for on-chain data. Ordinals inscriptions and BRC-20 tokens store data in witness fields. Track each protocol's count, volume, block share, fee revenue, and encoding overhead. Miner coinbase messages reveal pool identity and signaling activity.
Overview
Detected Embedded Data, Count
Daily average per block: OP_RETURN outputs and inscription-bearing witness items, by protocol
Detected Embedded Data, Volume
Daily average bytes per block by protocol, mixing exact OP_RETURN script bytes with estimated inscription payload
OP_RETURN
OP_RETURN Count
Daily average OP_RETURN outputs per block by protocol
OP_RETURN Volume
Daily average OP_RETURN bytes per block by protocol
OP_RETURN Protocol Share
Detected OP_RETURN outputs by protocol. Runes were 96.9% of them in 2024, the year they launched, and over 97% so far in 2026
Ordinals & Witness Data
Ordinals Inscriptions
Daily average inscriptions per block
Inscription Payload vs Envelope
Daily average inscription payload vs envelope overhead per block
Protocol Fee Competition
Daily fees paid by transactions matching each protocol detector. The detectors can match the same transaction, so these are not parts of one total
Miner Signals
Coinbase Message Length
Length of decoded ASCII text found in each block's coinbase transaction. Mining pools embed identifiers, timestamps, and occasionally custom messages in this space