Bitcoin Data Tracker
Monitoring OP_RETURN and Inscription data added to the Bitcoin blockchain
Blockchain Size
0 GB
OP_RETURN Outputs
0
Inscriptions
0
OP_RETURN Size
0 KB
Inscription Size
0 MB
Showing 0 blocks
Loading...
Data Count Over Block Height
About Bitcoin Data Tracker
Bitcoin Data Tracker monitors and visualizes arbitrary data embedded in the Bitcoin blockchain through OP_RETURN outputs and Ordinal inscriptions. This platform is provided solely for informational and analytical purposes, offering insight into on-chain data and activity trends.
OP_RETURN outputs allow arbitrary data to be embedded in Bitcoin transactions. Historically, node policy limited OP_RETURN data to 83 bytes. Starting with Bitcoin Core v30, the default relay policy was updated to permit OP_RETURN outputs of up to 100 KB, enabling nodes to relay transactions carrying larger data payloads. This change affects relay and mempool policy, not consensus rules — miners have always been technically capable of including larger outputs in blocks.
Inscriptions (Ordinals) leverage Bitcoin’s Segregated Witness (SegWit) and Taproot upgrades to store data within transaction witness fields. Although often associated with Taproot, inscriptions primarily rely on the SegWit architecture, which separates witness data from transaction signatures and assigns it a lower weight. This allows arbitrary content — such as images, text, and other digital artifacts — to be recorded directly within witness data, subject to transaction and block size limits.
The vertical line marks the release of Bitcoin Core v30, which significantly increased the default OP_RETURN relay limit from 83 bytes to 100 KB.
Important note: I do not encourage or endorse embedding non-monetary data in the Bitcoin blockchain. This information is provided solely for transparency, research, and educational purposes. Users should be aware that adding arbitrary data increases network load and is generally discouraged within the Bitcoin community.