Detected Embedded Data, Block Share
Share of block weight in detected protocol data, totalled over each day
Short ranges plot one point per block, about one every ten minutes. Longer ranges plot one point per day, computed from every block in that day. How it is computed depends on the chart: some average, some total the day up, some are a ratio of the day's sums, and each chart says which. Either way a brief spike inside a day is smoothed away.
About this metric
Definition
How much of a block is data rather than payments. Bitcoin has two places to put arbitrary bytes: an OP_RETURN output, which is a small amount of provably unspendable script, and the witness of a Taproot input, which is where inscriptions live. This is both, as a share of the block.
How it is measured
Combines OP_RETURN data (in outputs) and inscription data (in witness) as a percentage of the block's weight. Disjoint categories: an OP_RETURN output is non-witness and an inscription is witness, so they cannot overlap and their shares add.
Both sides are the cost to the block rather than the payload. OP_RETURN counts the whole output, script plus its 8-byte value and length prefix, at four weight units per byte. Inscriptions count the whole witness item, envelope and content-type included, at one. Weight is the denominator because it is what the block is rationed in; against size the two would be priced as the same good and the larger of them would change.
Measured from my own Bitcoin node. Methodology