Mempool Archive
Blocknative actively maintains the most comprehensive historical dataset of mempool transaction events within the Ethereum ecosystem. This collection contains transaction detection events since November 1st, 2019.
Blocknative logs all mempool transactions from nodes in multiple geographical regions for the Ethereum mainnet blockchain.
It is updated daily at 13 UTC time with a typical update containing 11M events for a 0.012TB size, though the heaviest days on the network can be as large as 41M events and 0.3TB size.
This uninterrupted dataset covers major scenarios the network has encountered over the years, including massive surges in traffic, huge gas spikes, bidding wars, the launch of MEV-boost, the price of ETH collapsing, EIP-1559, Black Thursday, and major hacks.
This data covers 27 data fields, such as gas details, input data, time pending in the mempool, failure reasons, and regional timestamps for each instance seen by our global network of nodes.
Our self-operated infrastructure provides the earliest detection times from North America, Asia, and Europe.
Getting Started
Each date has been partitioned into its own folder named in YYYYMMDD
format. Within each date partition, there are 24 files, named by two digit hour (ie 02.csv.gz) that the transaction event was detected in. These files are tab delimited gzipped csvs.
For example, if you wanted to access transactions on June 16th, 2023 from 12pm-1pm, your URL would be: archive.blocknative.com/20230616/12.csv.gz
How to download
Query, download and store the data slices locally using the steps below:
Fetching a full day of data
Here is a script you can use to download all slices in a day on your computer. Just modify with the DATE
Save this script to a file, for example, download_slices.sh
, and make it executable using the following command:
Then, run the script by executing:
Fetching on a custom range
Here is a script you can use to (1) download all hourly slices in a specific range of days on your computer, or (2) all specific hourly slices on a specific day.
Options:
-date-range
: for downloading full hourly slices for all days within this range (both dates inclusive). Format:YYYYMMDD-YYYYMMDD
For date range:
./download_mempool.sh --date-range YYYYMMDD-YYYYMMDD
-hour-range
: for downloading data for specific hours on a particular day. Format:YYYYMMDD:HH-HH
For hour range:
./download_mempool.sh --hour-range YYYYMMDD:HH-HH
Save this script to a file, for example, download_mempool.sh
, and make it executable using the following command:
Then, run the script by executing the command specified above the script.
Data Schema
Blocknative logs all mempool transactions from nodes in multiple geographical regions for the Ethereum mainnet blockchain. The Archive contains historic events for all transactions:
entering the mempool
denied entry into the mempool (rejection with reason)
exiting the mempool (eviction with reason)
replacing existing mempool transaction (speedup or cancel)
finalized on chain (confirmed or failed)
The number of times a transaction appears in the Archive corresponds to the number of status changes it undergoes. The detecttime
field indicates the time when the status change was first observed.
Below you can find the complete schema for the data:
Field Name | Description | Data Type | Example |
---|---|---|---|
detecttime | Timestamp that the transaction was detected in mempool. | timestamp |
|
hash | Unique identifier hash for a given transaction. | string |
|
status | Status of the transaction. | string |
|
region | The geographic region for the node that detected the transaction. | string |
|
reorg | If there was a reorg, refers to the blockhash of the reorg. | string |
|
replace | If the transaction was replaced (speedup/cancel), the transaction hash of the replacement. | string |
|
curblocknumber | The block number the event was detected in. | decimal(18,0) |
|
failurereason | If a transaction failed, this field provides contextual information. | string |
|
blockspending | If a transaction was finalized (confirmed, failed), this refers to the number of blocks that the transaction was waiting to get on-chain. | int |
|
timepending | If a transaction was finalized (confirmed, failed), this refers to the time in milliseconds that the transaction was waiting to get on-chain. | bigint |
|
nonce | A unique number which counts the number of transactions sent from a given address. | decimal(38,0) |
|
gas | The maximum number of gas units allowed for the transaction. | decimal(38,0) |
|
gasprice | The price offered to the miner/validator per unit of gas. Denominated in wei. | decimal(38,0) |
|
value | The amount of ETH transferred or sent to contract. Denominated in wei. | decimal(38,0) |
|
toaddress | The destination of a given transaction. | string |
|
fromaddress | The source/initiator of a given transaction. | string |
|
input | Additional data that can be attached to a transaction. This field can be used to tell a smart contract to execute a function. | string |
|
network | The specific Ethereum network used. | string |
|
type | Post EIP-1559, this indicates how the gas parameters are submitted to the network: - type 0 - legacy - type 1 - usage of access lists according to EIP-2930
- type 2 - using | int |
|
maxpriorityfeepergas | The maximum value for a tip offered to the miner/validator per unit of gas. The actual tip paid can be lower if ( | decimal(38,0) |
|
maxfeepergas | The maximum value for the transaction fee (including | decimal(38,0) |
|
basefeepergas | The fee per unit of gas paid and burned for the | decimal(38,0) |
|
dropreason | If the transaction was dropped from the mempool, this describes the contextual reason for the drop. | string |
|
rejectionreason | If the transaction was rejected from the mempool, this describes the contextual reason for the rejection. | string |
|
stuck | A transaction was detected in the queued area of the mempool and is not eligible for inclusion in a block. | boolean |
|
gasused | If the transaction was published on-chain, this value indicates the amount of gas that was actually consumed. Denominated in wei. | decimal(38,0) |
|
detect_date | A truncated version of | string |
|
blobversionedhashes | String representation of versioned blob hashes associated with the transaction's EIP-4844 data blobs. | string | 0x01f3ee17d9bd3b1e37df90813b95b21ec3504d66c5fe52974712bc4efb7db300 |
maxfeeperblobgas | The maximum total fee per blob gas the sender is willing to pay for blob gas in wei | decimal(38,0) | 242082408240 |
Frequently Asked Questions
What attribution must I provide when using the Blocknative Data Archive?
The archive is publicly available according to open data standards and licenses datasets under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International.
2.1 Attribution — End Users must give appropriate credit, provide a link to the license, and indicate if changes were made. End Users may do so in any reasonable manner, but not in any way that suggests the licensor endorses End Users or their use. 2.2 NonCommercial — End Users may not use the material for commercial purposes. 2.3 ShareAlike — If End Users remix, transform, or build upon the material, End Users must distribute their contributions under the same license as the original.
Please use the following as a guideline for attribution:
Papers: Data provided by Blocknative
If you have any questions please reach out to us on Discord.
What format is the data?
The data is stored in hourly slices with file format *.csv.gz
The data is tab delimited.
How many nodes are gathering mempool data?
We run highly redundant node infrastructure in each region to ensure strong uptime.
How can I identify on-chain transactions?
On-chain transaction have a confirmed
status.
How can I identify private transactions?
A private transaction does not have a pending
event. timepending
is determined from the difference between a transaction's pending
event and confirmed
event.
What is the difference between dropreason
and rejectionreason
?
dropreason
and rejectionreason
?A dropped transaction might have been valid but deemed less important or lower-priority. A rejected transaction is one that is fundamentally flawed or invalid according to the Ethereum protocol rules.
A drop reason could be that there isn't enough ETH in the EOA to cover gas fees. A rejection reason could be incorrect transaction signatures. Dropped transactions existed in the mempool, but are dropped to make room for incoming transactions. Rejected transactions never make it to the mempool.
Last updated