BitcoinDatabase.com
How it works
Bitcoin API Block explorer API Address lookup Historical data API Transaction API Bitcoin data API On-chain metrics Rich list Query with SQL Crypto AML API UTXO data Node API Webhook API Price API Transaction monitoring xpub balance API See all →
Glassnode alternative Blockchair alternative BlockCypher alternative Mempool.space alternative Xverse alternative BigQuery alternative Bitquery alternative TimechainIndex alternative CryptoQuant alternative Alchemy alternative QuickNode alternative Hiro alternative Amberdata alternative Elliptic alternative Merkle Science alternative Coin Metrics alternative CoinGlass alternative Crypto APIs alternative Tatum alternative NOWNodes alternative GetBlock alternative Arkham Intelligence alternative Santiment alternative Nansen alternative Allium alternative Flipside alternative SonarX alternative GoldRush alternative Scorechain alternative AMLBot alternative
Docs Pricing Blog Contact Sign in

Query the chain · Whale alerts

Bitcoin whale alert API for large transaction tracking

A whale alert is just a large bitcoin transaction that crosses a size you care about, tied to who moved it. The problem is that a raw feed of big transfers is noisy: an exchange shuffling its own cold storage looks identical to a real deposit unless you know the addresses behind both ends. The Bitcoin whale alert API solves that by combining every transaction on the fully-indexed chain with entity labels, so you can filter large transactions by value, by whether they touch an exchange, miner or known service, and by direction, then act on the ones that actually matter.

or try it below ↓

REST API · SQL · dashboards · address history from genesis

Query Console
btc
try:

Hit Run to query the Bitcoin blockchain.

Live from the chain for .

BTC

Balance trail

informational on-chain data · not financial advice

REST API · SQL · dashboards, one indexed dataset. Reading the chain ...

Set your own threshold, in BTC or in dollars valued against historical market data, and pull the matching transfers over REST, stream them to a webhook as new blocks confirm, or rebuild the history of large moves in SQL over the indexed chain, which grows with every new block. Because the transactions, their labels and the price series live in one schema, every alert traces back to the exact inputs and outputs behind it instead of a headline number. This is informational on-chain data and analytics, not a trading signal or investment advice.

REST API SQL DASHBOARDS WEBHOOKS CSV EXPORT

History from genesis queryable in seconds

On-chain data not financial advice

Why it works

What you get with Whale alerts

Alert on your own threshold

Define a whale as any transfer over the size you choose, set in BTC or in dollars valued against historical price, so a fund watching 500 BTC moves and a desk watching 10 BTC deposits each get the alerts that matter to them, not a fixed one-size feed.

Labels cut the noise

Every large transaction is checked against entity labels, so you can separate an exchange moving its own cold storage from a genuine deposit or withdrawal, filter to transfers that touch a specific exchange or service, and drop internal shuffles that are not real whale activity.

REST, webhooks and SQL

Poll recent large transfers over REST, push new ones to a webhook as blocks confirm, or reconstruct the entire history of big moves in SQL to backtest how whale activity lined up with flows, and trace any alert to its exact inputs and outputs.

What it handles

The indexed Bitcoin chain, queryable your way

Look up an address, a transaction, a UTXO, the rich list or an on-chain metric, by REST API, SQL or dashboard. The same authoritative data, reconciled block-by-block against the canonical chain, without running a node.

  • Detect large transfers over a BTC or dollar threshold
  • Label the exchange, miner or service on each side
  • Separate real deposits from internal cold-storage shuffles
  • Stream new whale moves to a webhook per block
  • Rebuild the history of large transactions in SQL over the indexed chain
GET /v1/address/{addr} query result
200 · JSON 
{
  "address": "bc1qxy2k…l0wdv8",
  "balance_btc": 68432.10,
  "balance_usd": 4612165420,
  "tx_count": 1284,
  "unspent_outputs": 37,
  "first_seen": "2014-02-09"
}
indexed from genesis · to the satoshi ✓ reconciled block-by-block

Why BitcoinDatabase

One platform, queryable three ways

Not a raw node to sync, not an indexer to build, and not five vendors to stitch together. The fully-indexed Bitcoin blockchain, available as a REST API, as SQL, and as dashboards, on one authoritative dataset.

REST API

Typed JSON for addresses, transactions, balances, UTXOs and metrics. Drop it into apps, wallets, explorers and agents with curl, Python or any HTTP client.

SQL access

Run SQL directly against the indexed Bitcoin dataset for ad-hoc analysis, cohorts and exports, the same data the API and dashboards read from.

Compliance-first

Informational on-chain data and analytics only. Entity labels and flow tracing are framed as tooling to support a regulated team's own review, not accusations.

Good questions

Questions about Whale alerts

There is no fixed cutoff; a whale transaction is simply a transfer large enough to matter for your use case, often hundreds or thousands of BTC, or a dollar value you set. The Bitcoin whale alert API lets you define the threshold yourself and values each transfer against historical price so the size is measured in dollars if you prefer.
By labeling both ends. A large transfer between two addresses that both belong to the same exchange is internal housekeeping, not a market event. Because BitcoinDatabase attaches entity labels to transactions, you can filter those out and keep genuine deposits, withdrawals and wallet-to-wallet whale moves. This is informational data, not a trading signal.
Set the filter on the age of the coins being spent rather than on the size of the transfer. A standing query for spends of outputs older than a chosen number of years fires a webhook when something long-dormant moves, which catches a 200 BTC transfer from 2012 that a pure size threshold set at 1,000 BTC would miss entirely.
No, and reading them as one is a common error. Size tells you how much moved, coin age tells you how long it had been still. A 5,000 BTC transfer between hot wallets happens constantly and means very little, while 50 BTC leaving an address untouched since 2011 is genuinely rare. The two filters catch different events and most desks run both.
Because a public feed sees transfers, not intent, and most large on-chain movements are not trades at all. Custody migrations, cold storage rotations, exchange consolidations and internal accounting all look like whale activity from outside. Labeling both ends of the transfer is what separates a deposit into an exchange from a wallet reorganizing itself.
It depends on what you are watching rather than on any standard figure. Desks tracking exchange deposits often start near 100 BTC because that is where individual flows begin to show up against background noise, while funds watching structural moves set it far higher. Start by measuring the distribution of transfer sizes over a recent month, then set the threshold at the percentile that gives you a volume of alerts you will actually read.
Yes, on the Scale plan. POST /v1/webhooks with the address and an https delivery URL, and each delivery is signed with a secret shown once when you create the hook. The subscription starts from the address transaction count and balance at that moment, so you are alerted on the next change rather than replayed its whole history.
Because most large transfers are an operator moving its own coins. On 22 September 2026 a tracked exchange cold address sent 24,828.5 BTC in two transactions. Tracing the outputs showed 14,000 BTC reached the same exchange hot wallet, 4,000 directly and 10,000 through one intermediate address, and 10,828.5 BTC went to fresh change addresses. A size-only alert would have reported a whale dump that never left the building.
On BitcoinDatabase, polling recent transactions and address balances over REST starts on Developer at $49 a month, 1 credit a lookup. SQL across every large output in the indexed chain starts on Growth at $199. Push webhooks on specific addresses and entity labels come with Scale at $799, which is the plan most desks watching exchange wallets end up on.
They overlap on large bitcoin transactions but differ in shape. Whale Alert is a real-time multi-chain alert feed with exchange attribution. BitcoinDatabase is a Bitcoin-native data layer where you query large transfers on your own thresholds, with entity labels, SQL over the indexed chain, REST and webhooks, rather than react to a fixed feed.
No. BitcoinDatabase is Bitcoin-only by design and indexes it deeply. Whale Alert streams alerts across many blockchains. If you need a broad multi-chain feed, Whale Alert fits that; if you need Bitcoin indexed deeply with large-transaction queries you drive yourself, that is what BitcoinDatabase provides.
No. Whale tracking tells you a large transfer happened, not what the price does next. A big exchange deposit does not guarantee a sale, and large holders are often early or wrong. Desks use whale flows as one input next to exchange reserves, SOPR and supply data, to add context to a decision rather than to trigger one.
Read every Bitcoin API question

Explore more

More ways to query Bitcoin with BitcoinDatabase

Bitcoin mempool and fee estimation API

Quote Bitcoin fee rates from live mempool state, then audit what your withdrawals actually paid.

Learn more

Bitcoin block explorer API

Power an explorer with blocks, transactions and addresses, no node to maintain.

Learn more

Bitcoin webhook API

Real-time notifications on address activity, incoming payments and confirmations.

Learn more

Bitcoin API

Query addresses, transactions and balances across the whole indexed chain in one call.

Learn more

Bitcoin address lookup

Look up any Bitcoin address: balance, full history and UTXOs in one query.

Learn more

Bitcoin historical data API

Full-depth history: every block, transaction and metric back to 2009.

Learn more

Buyer guides and measurements on this topic

Best Bitcoin API for Crypto Tax Software and Cost Basis Crypto tax software needs the USD value of every transaction at the moment it confirmed, and the Bitcoin chain does not contain it. On 8 September 202... Are Crypto Transactions Traceable? How Bitcoin Tracing Works Are crypto transactions traceable? Yes: Bitcoin is pseudonymous, not anonymous, and its public ledger lets analysts follow fund flows, cluster address...
See every use case See pricing Back to the Bitcoin API

Stop running a node. Just query Bitcoin.

Run your first query now and get on-chain data back by REST API, SQL or dashboard, with address history back to the genesis block over REST. Informational on-chain data only, not financial advice.

See pricing

History from genesis over REST · SQL · dashboards · addresses, transactions, UTXOs, metrics