Bitcoin Mempool Fees Scraper
Pricing
from $1.99 / 1,000 results
Bitcoin Mempool Fees Scraper
Bitcoin Mempool Fees Scraper is a Python tool designed to extract real-time mempool transaction fee rates, priority estimates (low, medium, high), and unconfirmed transaction counts from blockchain data providers. It exports structured cryptocurrency network fee datasets into clean format
Pricing
from $1.99 / 1,000 results
Rating
0.0
(0)
Developer
ZeroBreak
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
4 hours ago
Last modified
Categories
Share
Bitcoin Mempool & Fees Scraper — Bitcoin Fees, Blocks, and Mempool Statistics
Overview
Bitcoin Mempool & Fees Scraper collects publicly available Bitcoin network data, including recommended transaction fees, mempool statistics, recent blocks, and Bitcoin address activity.
Choose which data categories to collect, then review the results in an Apify dataset. Export the collected data as JSON, CSV, or Excel for analysis, reporting, and monitoring.
By default, the actor collects recommended transaction fees and mempool statistics.
Features
- Recommended transaction fees: Collect fastest, half-hour, hourly, economy, and minimum fee rates in sat/vB.
- Mempool monitoring: Retrieve pending transaction counts, virtual size, total fees, and fee-rate histogram data.
- Recent block information: Collect block hashes, heights, transaction counts, rewards, and mining pool details when available.
- Bitcoin address lookups: Retrieve confirmed and unconfirmed activity statistics for specified addresses.
- Configurable collection: Select one or more data modes and configure the number of recent blocks to include.
- Structured datasets: Store results in a format suitable for spreadsheets, dashboards, and data analysis.
- Duplicate reduction: Skip duplicate block hashes and repeated addresses during collection.
Use Cases
- Fee monitoring: Compare recommended Bitcoin transaction fee rates over time.
- Mempool analysis: Track pending transactions and changes in network congestion.
- Block monitoring: Review recent block heights, transaction counts, rewards, and mining pool information.
- Address analysis: Examine confirmed and unconfirmed activity statistics for a Bitcoin address.
- Spreadsheet reporting: Export fee snapshots and network statistics for further analysis.
- Monitoring workflows: Use collected data to support alerts and reports when fee rates or mempool size change significantly.
Input Parameters
| Parameter | Type | Default | Description |
|---|---|---|---|
modes | Array | ["fees", "mempool"] | Data categories to collect: fees, mempool, blocks, and address. |
addresses | Array | [] | Bitcoin addresses to look up when address mode is enabled. |
blockCount | Integer | 15 | Maximum number of recent blocks to retain from the available latest-block results. |
maxItems | Integer | 100 | Maximum number of dataset rows to collect. Maximum: 1000. |
Example Input
{"modes": ["fees", "mempool"],"addresses": [],"blockCount": 15,"maxItems": 100}
To include recent blocks, add blocks to the modes array.
To look up a Bitcoin address, enable address mode and provide one or more addresses:
{"modes": ["fees", "mempool", "address"],"addresses": ["1A1zP1eP5QGefi2DMPTfTL5SLmv7DivfNa"],"blockCount": 15,"maxItems": 100}
What Data Does This Actor Extract?
The actor produces structured dataset rows for each selected collection mode. Available fields depend on the mode and the data returned during collection.
Extracted Data Fields
| Field | Type | Description |
|---|---|---|
mode | String | Collection category: fees, mempool, blocks, or address. |
scraped_at | String | Timestamp indicating when the row was created, in UTC. |
fastestFee | Integer | Recommended fee rate for faster confirmation, in sat/vB. |
halfHourFee | Integer | Recommended fee rate for an approximate 30-minute confirmation target, in sat/vB. |
hourFee | Integer | Recommended fee rate for an approximate one-hour confirmation target, in sat/vB. |
economyFee | Integer | Lower recommended fee rate for transactions that can wait longer, in sat/vB. |
minimumFee | Integer | Reported minimum recommended fee rate, in sat/vB. |
count | Integer | Number of transactions waiting in the mempool. |
vsize | Integer | Mempool virtual size. |
total_fee | Integer | Aggregate mempool transaction fees, expressed in satoshis when supplied by the source. |
fee_histogram | Array | Fee-rate histogram data describing the mempool. |
id | String | Block identifier or hash. |
height | Integer | Block height. |
tx_count | Integer | Number of transactions in a block. |
size | Integer | Block size. |
weight | Integer | Block weight. |
difficulty | Number | Reported mining difficulty. |
reward | Number | Block reward value, as returned by the source. |
medianFee | Number | Reported median transaction fee rate for a block. |
totalFees | Number | Total transaction fees reported for a block. |
poolName | String | Mining pool name, when available. |
address | String | Bitcoin address being examined. |
chain_stats fields | Object fields | Confirmed transaction and value statistics, flattened into columns where available. |
mempool_stats fields | Object fields | Unconfirmed transaction and value statistics, flattened into columns where available. |
Block rows can also include additional transaction counters and block statistics when available. Large raw hexadecimal values, such as coinbase transaction data and block header hex, are excluded from the standard tabular output.
Example Output
A fee-mode dataset row may look like this:
{"fastestFee": 1,"halfHourFee": 1,"hourFee": 1,"economyFee": 1,"minimumFee": 1,"mode": "fees","scraped_at": "2026-10-12T00:00:00+00:00"}
The numeric values above are illustrative examples, not live fee recommendations.
Data by Mode
| Mode | Data collected |
|---|---|
fees | Recommended Bitcoin transaction fee rates. |
mempool | Pending transaction totals, virtual size, fee totals, and fee histogram. |
blocks | Recent block information, including height, hash, transaction counts, rewards, and mining pool details when available. |
address | Confirmed and unconfirmed activity statistics for each supplied Bitcoin address. |
Working with Your Dataset
After the actor finishes running:
- Open the actor's dataset.
- Review the collected rows and fields.
- Export the results as JSON, CSV, or Excel.
- Use the exported data for reporting, historical comparisons, or your own analysis workflows.
Important Notes
- Fee rates and mempool statistics change as Bitcoin network conditions evolve. Each run represents data available at collection time.
- The recent-block collection uses the latest available block results. It does not provide comprehensive historical block pagination.
- The configured
blockCountcontrols how many of the available recent blocks are retained; it does not retrieve an unlimited block history. - Address lookups require valid Bitcoin addresses.
- The fields returned for blocks and addresses can vary depending on the available data.
- The actor does not provide transaction-ID lookups.
FAQ
How often should I collect fee data?
That depends on your monitoring needs. Run the actor periodically to build a history of fee rates and mempool conditions.
Can I collect only block data?
Yes. Set modes to ["blocks"] to focus on recent blocks.
Can I look up multiple Bitcoin addresses?
Yes. Enable address mode and provide the addresses in the addresses array.
Why does the actor return only a limited number of recent blocks?
The collection uses the latest available block results rather than traversing older block heights. The blockCount parameter controls how many of those recent results are retained.
Can I export the results for analysis?
Yes. The Apify dataset can be exported as JSON, CSV, or Excel.
Disclaimer
This actor is an independent data collection tool and is not affiliated with or endorsed by mempool.space or Bitcoin. Data availability and accuracy depend on the publicly available information at collection time. Verify important figures independently before using them for financial or operational decisions.
Is Web Scraping Legal?
Collecting information that is already public is generally legal. Scraping is not the same thing as hacking, and there is no single law that bans it. The limits are the usual ones: do not break into accounts, do not take private or confidential data, and be careful with personal data and copyrighted works. A site's terms can also restrict how you access it. Facts such as a public name, price, or rating are not the same thing as republishing someone's article or photo.
This actor collects information from public pages. It does not log in and it does not bypass access controls.
For a longer explanation, see Apify's article Is web scraping legal?.