Request: How many mempool transactions are evicted by time?

Following up with some numbers. I took @b10c’s reason=expiry extract and ran the whole set through a confirmation scan against an archival node. Across the full window (2024-02-16 to 2026-10-21, 938,157 of unique expired transactions):

  • 92.0 percent (863,451) were later mined; only 8.0 percent (74,706) never confirmed.
  • At least 34 percent (316,381) show rebroadcast evidence, and 87 percent of those confirmed.
  • Of the ones that confirm, half are mined within about 5 days of first expiry and ninety percent within about 55 days, so there is a long tail that bounces for weeks before getting in.

Nearly everything time-based expiry evicts is mined anyway, alot of it after a rebroadcast. @rustaceanrob’s indeed expiry causes unnecessary relay bandwidth.

On “expired then replaced”: @b10c I don’t think the logs can catch it. Once a transaction expires it is already evicted, so a later conflicting transaction is never logged as replacing it, there is nothing in the mempool to replace. The only way would be to take the expired transaction’s spent outpoints and check whether a later mempool entry or mined transaction spends them, which needs data the txid-only logs don’t carry. Given 92 percent confirm anyway the lost ones are minuscule of a concern, but it is the one piece this dataset can’t answer.

Reproducer and more graphs: GitHub - ismaelsadeeq/mempool-expiry: mempool-expiry-analysis · GitHub