Cookie

By using this site you consent to accept Mesmer Data LLC's analytics and functional cookies.
Read more by clicking 'Cookie Settings' here, or in the bottom menu.

BTC - Block Size, BRC-20-Adjusted (Bytes)

Description

The Bitcoin Block Size (BRC-20-Adjusted) shows the average size in bytes of blocks for each time interval, excluding BRC-20 transactions. Unadjusted Block Size shows the adjustment's effect.

Adjusted data starts at BRC-20's first block: 767430 (Dec 14, 2022)

Bitcoin's USD Market Price is included for reference.

Pseudocode

for each block in blockchain:
  block.size_adj := block.size - sum(block.brc20_tx[].size)
  (x,y1) := (block.time, block.size)
  (x,y2) := (block.time, block.size_adj)

for each hour in blockchain:
  hr_blk_size := avg(blockchain[hr_start:hr_end].size)
  hr_blk_size_adj := avg(blockchain[hr_start:hr_end].size_adj)
  (x,y1) := (hour, hr_blk_size)
  (x,y2) := (hour, hr_blk_size_adj)

for each day in blockchain:
  day_blk_size := avg(blockchain[day_start:day_end].size)
  day_blk_size_adj := avg(blockchain[day_start:day_end].size_adj)
  (x,y1) := (day, day_blk_size)
  (x,y2) := (day, day_blk_size_adj)

Technical Info

Block size is calculated by summing up the size in bytes of the block header, transactions, and witness data (if SegWit).

For non-SegWit blocks, block size and stripped size are the same. Witness data plus stripped data makes up each block's total size.

Before SegWit was introduced (July 2017, block height 477,120), Bitcoin's max block size was set at 1 MB (1,000,000 bytes). With SegWit, the theoretical maximum is 4 MB. Since SegWit, not all blocks produced are SegWit blocks; some miners don't like the reduced rewards, and since SegWit is a soft fork miners can choose whether they want to utilize it or not.

Block size is a network activity indicator. In particular, the noticable reduction of variance with sustained high block sizes indicates network saturation. Applying moving averages reduces variance and makes saturation appear as a sustained high moving average value.

The results of this adjustment to the block size data suggests that non-inscription transactions have not been hindered from getting processed by the saturation of mempool since BRC-20's inception.

  • Hourly and daily aggregations are derived from block data using average for this metric.
  • Hourly data contains occasional gaps; no blocks were generated during these times.

Disclaimers

This site is currently in Beta, and there will likely be some bugs. If you find any, please check out the FAQ first, and then let us know! Thanks! Chart views are saved between visits, so if you have any display issues and want to reset your chart view, click here.

This site is for informational use only. Users are required to conduct their own analysis, draw their own conclusions, and make their own financial decisions. Consult with qualified professionals before making investments. This service is not intended as legal, financial or investment advice. For full details please visit our Disclaimers page.