Blockchair Scraper

Most on-chain tooling is EVM-first and treats Bitcoin as an afterthought, which leaves the UTXO chains poorly served. Blockchair indexes them properly, and this Actor reads it two ways: chain statistics (block height, 24h transactions, hashrate, mempool, difficulty, market cap) and address dashboards (balance, transaction count, first and last received).

What it does

• Covers the UTXO chains properly: Bitcoin, Litecoin, Dogecoin, Bitcoin Cash and the others Blockchair indexes, rather than treating them as an EVM afterthought.
• Two routes on the same input: stats for chain-level health and address for a single wallet.
• Reports network health, not just prices: hashrate24h, difficulty, mempoolTransactions and block height in one record.
• Gives an address its history window: firstSeenReceiving and lastSeenReceiving, so a dormant wallet is obvious.
• Reads several chains in one run, so a multi-chain dashboard is one call rather than one per chain.
• Takes an optional API key, which Blockchair requires for the address route. Chain stats work without one.

Use cases

You need to	How this Actor does it
Monitor network health	Read hashrate24h and difficulty on the stats route and chart them
Watch for mempool congestion	Read mempoolTransactions on a short schedule
Check a Bitcoin wallet balance	Use the address route with your Blockchair key
Spot a dormant wallet waking up	Compare lastSeenReceiving against the previous run
Build a multi-chain dashboard	Pass several chains in one run and read the same fields for each
Feed an on-chain research agent	Call the Actor over MCP and let the model ask for a chain or address

Quick start

1. Click Try for free.
2. Add your chains, one per line: bitcoin, litecoin, dogecoin, bitcoin-cash.
3. Leave Route on stats for chain-level data. For the address route, add your addresses and paste a Blockchair API key, which Blockchair requires for that route.
4. Click Start. Rows appear within seconds.
5. Export as JSON, CSV, Excel or XML, or read the dataset over the API.

Input

Field	Type	Default	What it controls
chains	array	bitcoin	Which Blockchair chains to read
route	string	stats	stats returns chain-level health, address returns a wallet dashboard
addresses	array	empty	Addresses to read on the address route
apiKey	string	empty	Blockchair API key. Required for the address route, not for stats
maxItems	integer	0	Caps how many records are written. 0 writes them all

{
    "chains": [
        "bitcoin",
        "litecoin",
        "dogecoin"
    ],
    "route": "stats",
    "maxItems": 0
}

Output

One dataset item per chain on the stats route, one per address on the address route. The dataset has a view for each, so the console shows the right columns for what you asked for.

Field group	Fields
Always	status, chain, url
Stats route	blocks, transactions24h, hashrate24h, difficulty, mempoolTransactions, value, currency, marketCap
Address route	address, balance, transactionCount, firstSeenReceiving, lastSeenReceiving
Timing	validFrom, scrapedAt

{
    "status": "ok",
    "chain": "bitcoin",
    "blocks": 918442,
    "transactions24h": 412088,
    "hashrate24h": "881.4 EH/s",
    "difficulty": 128841002991172,
    "mempoolTransactions": 18422,
    "value": 104238.61,
    "currency": "USD",
    "marketCap": 2068442110394,
    "validFrom": "2026-09-06T05:30:00.000Z",
    "url": "https://blockchair.com/bitcoin"
}

Integrations

Run it over the API and get the rows back in one call:

curl -X POST "https://api.apify.com/v2/acts/publicmoney~blockchair-scraper/run-sync-get-dataset-items?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"chains": ["bitcoin", "litecoin", "dogecoin"], "route": "stats", "maxItems": 0}'

From Python:

from apify_client import ApifyClient

client = ApifyClient("YOUR_TOKEN")
run = client.actor("publicmoney/blockchair-scraper").call(run_input={"chains": ["bitcoin", "litecoin", "dogecoin"], "route": "stats", "maxItems": 0})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item["value"], item["validFrom"])

Give an AI agent the Actor over MCP:

{
    "mcpServers": {
        "apify": {
            "url": "https://mcp.apify.com/?actors=publicmoney/blockchair-scraper"
        }
    }
}

Schedules run it on any cron, webhooks fire when a run finishes, and platform integrations push the dataset to Google Sheets, Slack, Airtable, Zapier or your own endpoint.

Cost

Pay per event, so you pay for records rather than compute time.

Event	Free tier	Top volume tier
Record with data	$0.002	$0.0007
Actor start	$0.00005 per GB	Same

A record that returned no data is published as a failure row and is never charged. Six volume tiers apply, so the per-record price falls with monthly volume.

Troubleshooting

Issue	Solution
The address route returns failed for everything	Blockchair requires an API key for that route. Paste one into API key. Chain stats work without it.
A chain returns failed	Blockchair does not index it under that name. Chain names are Blockchair's own slugs, such as bitcoin-cash rather than bch.
An address returns failed on a chain that works	The address format does not match the chain. A Bitcoin address is not a Litecoin address.
firstSeenReceiving is missing	The address has never received funds, so there is no first receipt to report.
hashrate24h is a string, not a number	Blockchair publishes it with its unit, such as 881.4 EH/s, and the Actor keeps the source value rather than guessing an exponent.

FAQ

Do I need a Blockchair API key?

For the address route yes, because Blockchair requires one there. Chain statistics work with no key at all. Paste the key into the API key field, which is stored as a secret.

Which chains does it cover?

The chains Blockchair indexes, which is where its strength lies: Bitcoin, Litecoin, Dogecoin, Bitcoin Cash and the other UTXO chains. For EVM chains and Solana use the Blockchain Scanner Actor in this fleet.

Why use this over the Blockchain Scanner Actor?

Different coverage and different data. Blockchain Scanner does addresses, transactions and tokens across nine mostly EVM chains. This one does chain-level network health, hashrate, difficulty and mempool, which Blockchain Scanner does not read at all.

Can I get transaction history for an address?

Not here. The address route returns a balance summary. For a transaction list use the Blockchain Scanner Actor on a chain it supports.

Does it return historical chain stats?

No, stats are current. Schedule the Actor and let the dataset accumulate to build a series of hashrate, difficulty and mempool over time.

Do I need a Blockchair API key?

No. You need an Apify token to call the Actor over the API. No Blockchair credential is involved anywhere.

Can I get this data in Python?

Yes, with the apify-client package as shown above. It returns parsed JSON, so there is no HTML or response handling on your side.

Can I get the data into Excel or Google Sheets?

Yes. Export the dataset as XLSX or CSV, or connect the Google Sheets integration so each run appends to a sheet.

Can an AI agent call this Actor?

Yes. Add it to an MCP client with the config above and the model can request what it needs on its own. Every record is flat JSON with named fields, so no post-processing is needed.

Is it legal to scrape Blockchair?

Blockchain data is public by design and this Actor reads Blockchair's public pages and API. Addresses are pseudonymous rather than anonymous, so if you link one to a named person you are handling personal data and your own privacy obligations apply. Take your own legal advice for your use case.

Changelog

• 0.0.2 Added the address route with the first and last received timestamps.
• 0.0.1 First release. Chain statistics across the indexed chains.

Feedback

Found a field Blockchair publishes that this Actor misses, or an input it rejects? Open an issue on the Issues tab with the input and what you expected. A daily test runs every Actor in the fleet against live sources, so parser fixes ship fast.