Follow mempool research on nostr!

nostr:npub1m7qjg4hsa2q32rtekewpdn54guh508tlh6ztml7ssluj6vgflensy6m4gz

Check out our inaugural mempool research report which dives deep into the empty block phenomenon!

https://research.mempool.space/empty-block-report

yes -- at the moment, block health is intended to be a measure of intentional *exclusion*

https://mempool.space/docs/faq#what-is-block-health

Default core policy is to treat each Sigop as though it has a 20 byte size. These transactions with many sigops are therefore treated as though they have a lower fee rate.

The linked transactions have a large number of sigops (241).

Default bitcoin core transaction selection treats sigop's as though they have a larger size than they do. This means that these transactions are treated as though they have a significantly lower fee rate (half in this case)

https://github.com/bitcoin/bitcoin/blob/82ba0f80a0b56bb160c8be1fddd82dbbc4fb3947/src/policy/policy.h#L37

static constexpr unsigned int DEFAULT_BYTES_PER_SIGOP{20};

Thanks, investigating.

2024 is the year we accelerate

Sign up to get notified when Mempool Accelerator launches.

https://mempool.space/signup

Thanks for the bug report.

If possible please can you share the device and browser you are using via DM

Working on it!

Introducing Mempool Goggles!

Have you ever wished you had x-ray specs to see exactly what's inside the mempool?

No, me neither, but we built you a pair anyway.

#m=image%2Fjpeg&dim=893x900&blurhash=%7CAGjj%3D%2BwDgE01OKHD%7D-%40%238o%5Df-sFr%3ASJa*xGX8NFD4S%5Eb%24gRT3rY%255Z%7CO%3FrxwHJNKR%24%2BfzJ7nNxcOtWHg9nJj9TKi%5DW%3DV%40nMbuxwnNNHe%3AoHkCWS5ts*xlR%3Az%3FajT0bvS%24ktNHnLt7NZw%40R%3BT1w%5EJENem*XUPD%23%7Es%2BnOr%3F&x=a1f1c72026d28ee865cc29a3c2a0da3bfe676f5f3ad35374b9f1898f27a17e02

Click on the Mempool Goggles icon at the top left of the mempool block visualization to reveal the new filter menu.

There are 25 different categories to explore, or mix-and-match to narrow down your focus even further.

#m=image%2Fjpeg&dim=669x680&blurhash=%7C29ZWg*JS6XR9_In0zRO0f-%3AoM%251kWkXs%2CR.w%5BIV9EMdtlWYbHxao%23xtj%5E%25Ms%3Bt7V%40kCoeRjt6R-9ERPoyV%40tlt7ogxaa%23VrM%7Bg3bIR*oLbct7o2EhV%40ofogf5ofV%40o0ofIAR%25R%2BaKWBflj%3FW%3DxtGbs%3ARPWVZ%7ER*slR-t6&x=78b74823e7a3f02cefef36ed5c2f7eb2ef596bae239446ff995de73ec8efd13a

Want to see how much of the mempool is occupied by monkey jpegs? Try the "Inscription" filter.

Curious how many transactions use both RBF and CPFP to bump fees? Hit the "Replacement" and "Pays for parent" filters.

#m=image%2Fjpeg&dim=669x680&blurhash=%7C29PQd%5Ek1PNZ0%7CaIEfNGxHtTx%5ExuoIacRhRiaeo3Bqkr%252oIjDngngniWXOtT1X9sls8ngr%3DWBS4BWXAxaj%3Fn%23nhWAaxWXs%3BShoLxFS1axf5S2WWE%25WBjYa%7Ds%3Aofs%3AW%3BS2V%3FV%3FjEWXSis%3Bs%3BofWoM%7BV%3DnhS5S%24bdogs%3AoJ&x=81cf8255ab24c9456ed933da5f475b24f76334c8d3e20637aad3420af5f108f7

From simple mempool analysis to advanced technical insights, Mempool Goggles has something for everyone.

Check it out now on the mempool block page

https://mempool.space/mempool-block/0

block health is not intended to be a measure of how closely an expected block resembles an actual block. The actual block can be vastly different from the expected block, but if no transactions appear to be intentionally excluded, it will have a high health rating

https://mempool.space/docs/faq#what-is-block-health

There is no API call for the number of mempol blocks, but this can be estimated by dividing the sum of the vBytes in the mempool by 1,000,000

The number of unconfirmed transactions can be called directly.

Here is a python example:

import json

import requests

import math

# Approximate number of blocks in mempool.space's mempool

total_blockVSize = sum(item['blockVSize'] for item in requests.get('https://mempool.space/api/v1/fees/mempool-blocks').json())

block_count_estimate = math.ceil(total_blockVSize/1000000)

print("Unconfirmed block count: ", block_count_estimate)

# Get transaction count

transaction_count = requests.get("https://mempool.space/api/mempool").json()['count']

print("Transaction count:", transaction_count)

👌

oh calculator not clock 🤦‍♂️

hey, go here:

https://mempool.space/clock/

fwiw there's a small clock icon on the graphs page (https://mempool.space/graphs) if you find that easier

You can observe many transactions being broadcast with lowball fees well below that required to enter the next block, increasing the unconfirmed transaction count but not affecting the fee rate

Recent median fee rates are below 20 sat/vB despite the presence of over 557,000 unconfirmed transactions in our mempool.

👀

update: sorry fam...sadly, the mempool maintainers didn't see us eye-to-eye on this

https://github.com/mempool/mempool/pull/3927