BitcoinDatabase.com
How it works
Bitcoin API Block explorer API Address lookup Historical data API On-chain data Transaction API Bitcoin data API Wallet tracker On-chain metrics Rich list Address balance API Query with SQL Crypto AML API UTXO data Blockchain API Flow analysis Node API Webhook API Price API Transaction monitoring Mempool API RPC API xpub balance API See all →
Glassnode alternative Dune alternative Blockchair alternative Chainalysis alternative BlockCypher alternative Chainstack alternative Blockchain.com API alternative Mempool.space alternative CoinAPI alternative TRM Labs alternative Whale Alert alternative CoinGecko alternative CoinMarketCap alternative Blockdaemon 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

Compliance & flows · Transaction monitoring

Crypto transaction monitoring API for Bitcoin AML and risk

Crypto transaction monitoring starts with data your team can trust and query on demand. BitcoinDatabase exposes addresses, transactions, balances, UTXOs, entity labels and fund flows over a REST API with full address history back to 2009, plus SQL and dashboards over the indexed chain, which grows with every new block, so your compliance stack reads from one reconciled source instead of scraping block explorers.

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

Screen a deposit address before you credit it, trace the path funds took across hops, check exposure to labeled exchange, mixer or service clusters, and pull the on-chain evidence an analyst needs to review a case. Everything here is informational on-chain data and risk signals to support your own review. It is not an accusation, a deanonymization claim, or legal advice, and your team makes the decision.

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 Transaction monitoring

Screen addresses and flows

Look up any address for balance, history and UTXOs, then follow inputs and outputs hop by hop to see where funds came from and went, all from the indexed chain.

Entity labels and exposure

Where an address clusters to a known exchange, miner, mixer or service, we attach a label as informational context so your analysts can assess exposure, never as an identity claim about a person.

Built for a review workflow

Pull the raw on-chain evidence a case needs over REST for your platform, SQL for investigations and dashboards for review, so monitoring, alerting and audit all read one dataset.

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.

  • Screen a deposit or withdrawal address before you act
  • Trace fund flows across multiple transaction hops
  • Assess exposure to labeled exchange, mixer or service clusters
  • Pull on-chain evidence to support an analyst review
  • Feed a REST API, SQL or dashboards from one indexed source
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 Transaction monitoring

Four layers, and only two of them are chain data. Raw ledger facts: addresses, transactions, inputs, outputs, balances and UTXOs. Derived structure: clustering, flow paths and hop counts. Attribution: which real entity a cluster belongs to. And your own policy: thresholds, typologies and escalation rules. The first two are arithmetic anyone can reproduce. The third is off-chain evidence, and it is the part vendors charge for.
Watch unconfirmed, decide on confirmed. Seeing a deposit the moment it broadcasts buys your team time to prepare a review, but an unconfirmed transaction can still be replaced. We sampled 260 live mempool transactions on 16 September 2026 and 232 of them signalled replace-by-fee. Alert on the broadcast, credit on the block, and record which block height the decision was made at.
Group by funding source rather than by amount. A single tiny receive is noise. On 16 September 2026 we watched one address pay exactly 546 satoshis into two unrelated exchange cold wallets in consecutive blocks, with identical fees and identical virtual sizes. That pattern, one source touching many destinations with an identical value, is the alert. Our dust attack detection page covers the thresholds per script type.
Far enough to reach a labeled entity, and no further than you can defend. Each hop multiplies the candidate set and dilutes the connection, so a five hop path to a sanctioned address is not comparable evidence to a direct one. Record the hop count and the value share on every finding, because a reviewer needs to weigh them, and a monitoring system that reports exposure without distance is reporting a number nobody can act on.
Not from the chain. Clustering can show that a set of addresses probably shares an owner, using common input ownership and change heuristics, and that is reproducible arithmetic. Putting a name on the cluster requires off-chain evidence: a deposit somebody made from a known account, a published address, a subpoena. We provide the on-chain layer and the labels we can support, as informational context for your own review.
Because they are running different address lists and different clustering, not different mathematics. The chain facts are identical and nobody disputes them. What differs is which addresses each vendor believes belong to which entity, and those lists are proprietary and rarely published. Ask any vendor how the verdict was reached and whether you can reproduce it from rows they will hand you.
The block height, not the timestamp. Bitcoin block timestamps are not monotonic, and when we measured spent output lifespans across a block we found 15 inputs with a negative lifespan because the spending block carried an earlier timestamp than the block that created the coin. Pin every decision to a height and a block hash, store the raw evidence alongside the verdict, and your work is reproducible a year later.
It surfaces the on-chain facts behind an address or transaction: balance and history, the path funds took through inputs and outputs, current UTXOs, and any entity label such as exchange or mixer. These are informational risk signals to support your team's own review, not an accusation or a determination about a person.
Large exchanges usually license Chainalysis KYT, TRM Labs or Elliptic by quote for multichain attribution. Smaller multichain businesses look at AMLBot or Scorechain. A Bitcoin-only program can run SDN screening with one and two hop exposure on our Enterprise plan at $1,498 a month, and many teams pair a broad vendor with a high-volume Bitcoin screen that keeps the transaction behind every finding.
$2,000. Money services businesses, which FinCEN guidance FIN-2019-G001 says includes money transmitters of convertible virtual currency, must report suspicious transactions of $2,000 or more under 31 CFR 1022.320, well below the $5,000 bank threshold. At bitcoin prices that covers almost every transfer, so monitoring has to read nearly all deposits and withdrawals, not a sample.
Yes. Every Bitcoin transaction is recorded on a public ledger, so balances and the flow of funds between addresses can be followed. BitcoinDatabase indexes that ledger and adds entity labels, giving compliance teams the data to trace exposure. It does not identify individuals and is not legal advice.
Read every Bitcoin API question

Explore more

More ways to query Bitcoin with BitcoinDatabase

Bitcoin dust attack detection

Dust limits per script type, dust transaction data, and the spray patterns behind address poisoning.

Learn more

Crypto AML API

Risk signals, exposure and entity labels to support your compliance review.

Learn more

Bitcoin double spend detection API

Detect conflicting and replaced transactions before you credit an unconfirmed Bitcoin payment.

Learn more

Bitcoin webhook API

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

Learn more

Bitcoin address types

Script type on every input and output: legacy, P2SH, native SegWit and Taproot, counted and valued.

Learn more

Bitcoin exchange reserves

Exchange balance and reserve totals per address, with dated snapshots and the transactions behind every move.

Learn more

Buyer guides and measurements on this topic

Crypto KYT Software for Exchanges and Money Transmitters Crypto KYT software screens every deposit and withdrawal before you credit or sign. On 8 October 2026 the 531 valid Bitcoin addresses on the OFAC SDN... Crypto ATM Regulations by State and Wallet Screening Software Crypto ATM regulations now cap daily amounts, fees and refunds in most kiosk states, and six statutes require operators to block wallets linked to fra... Best Bitcoin Collateral Monitoring API for Crypto Lenders The best Bitcoin collateral monitoring API for a crypto lender watches collateral outpoints rather than addresses and returns the balance at a named b...
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