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.

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 full history of large moves in SQL. 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.

or try it below ↓

REST API · SQL · dashboards · indexed from genesis

Query Console

BTC address or sample query

btc

try:

Hit Run to query the fully-indexed Bitcoin blockchain.

BTC

30-day trend

informational on-chain data · not financial advice

REST API · SQL · dashboards, one indexed dataset. Querying the indexed Bitcoin blockchain ...

REST API SQL DASHBOARDS WEBHOOKS CSV EXPORT

Indexed 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 full history of large transactions in SQL

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 our SDKs.

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.

Read every Bitcoin API question

Explore more

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, indexed from the genesis block. Informational on-chain data only, not financial advice.

See pricing

Indexed from genesis · REST · SQL · dashboards · addresses, transactions, UTXOs, metrics