BitcoinDatabase.com
All posts
Compliance

How to Screen a Bitcoin Address for Sanctions and Risk

How to screen a Bitcoin address for sanctions: check it against OFAC and other lists, trace exposure to high-risk entities, and turn the result into a risk decision your compliance team can defend.

By the BitcoinDatabase team

July 2026 · 9 min read

The short answer

To screen a Bitcoin address for sanctions, check it against published lists such as OFAC's SDN list, then trace its on-chain counterparties to measure exposure to entities your program treats as high risk, and record a decision. Do this at three moments: before onboarding a wallet, before clearing a transaction, and on an ongoing basis when lists update. Direct list matches are the clearest hits, but most real risk is indirect, coins one or two hops from a sanctioned cluster, mixer, or flagged service. Good screening surfaces both, attaches the evidence, and leaves the judgment to a human reviewer rather than auto-blocking on a raw score.

Sanctions screening in crypto is a legal requirement for regulated US businesses, not a nice-to-have. Facilitating a transaction for a sanctioned party can trigger penalties even when it is unintentional. The chain is public, so the data to catch exposure exists; the work is turning an address into a defensible decision.

What is Bitcoin address screening?

Address screening is the process of checking whether a Bitcoin address is linked to a sanctioned or high-risk party before you do business with it. It combines two things: list matching, comparing the address against government-issued lists like OFAC, the EU, and the UN, and exposure analysis, tracing the address's transaction history to see whether its coins came from or went to labeled high-risk entities. The output is a risk signal plus the evidence behind it, which a Bitcoin address screening API can return in one call from the indexed chain.

When should you screen an address?

Screening should happen at a minimum at three points, which map to OFAC's expectations for a risk-based program.

When Why
At onboarding Catch a sanctioned or high-risk wallet before it enters your book
Before each transaction A clean wallet can receive tainted coins later; check at the point of movement
Ongoing, on list updates New designations can implicate addresses you already cleared

How does sanctions screening work step by step?

First, match the address directly against current sanctions lists, including near-matches so an aliased or slightly altered identifier is not missed. Second, walk the address's transaction graph to find its counterparties and check whether any are labeled sanctioned entities, mixers, or high-risk services. Third, measure indirect exposure: coins that reached the address one or two hops from a flagged cluster still carry risk even when the address itself is not listed. Fourth, combine these into a risk signal. Fifth, route anything above your threshold to a human analyst who reads the evidence and records the decision. This is how a transaction monitoring workflow stays defensible.

What is direct vs indirect exposure?

Direct exposure is a transaction straight to or from a sanctioned or high-risk address, the clearest and most serious hit. Indirect exposure is risk that reaches an address through intermediaries: the coins passed through a mixer, a flagged exchange deposit, or a chain of hops originating at a designated cluster. Indirect exposure is where most real screening value lives, because sophisticated actors rarely transact directly and rely on obfuscation to put distance between themselves and a clean-looking wallet. Screening that only checks direct list matches misses the majority of genuine risk.

Can a risk score block a customer automatically?

A score should inform a decision, not make it alone. Exposure analysis produces signals, not verdicts: an address can receive high-risk coins without its owner having any connection to wrongdoing, and a low score does not prove innocence. A sound program routes elevated signals to a trained reviewer who examines the underlying transactions, weighs context, and documents the rationale. Building that review discipline is a core part of a compliance program that can stand up to an examiner. Automating a hard block off a raw number invites both false positives and missed nuance.

What data do you need to screen an address?

You need three things: current sanctions and risk lists, entity labels that identify exchanges, mixers, and services on-chain, and the full transaction graph so you can trace exposure across hops. Reconstructing that yourself means running an indexed node, maintaining address labels, and ingesting list updates. The alternative is querying an indexed provider that already holds labeled addresses and raw transactions in one schema, so a screen returns both the signal and the exact flows behind it, and an analyst can drill from the score straight to the evidence.

Is address screening the same as accusing someone?

No. Screening surfaces on-chain exposure and list matches as context for a compliance team's own review. It is not an accusation, a legal determination, or a claim about any individual's conduct, and a risk signal is a starting point for investigation, not a conclusion. BitcoinDatabase provides informational on-chain data and analytics only; it is not legal advice. Your program's policies, and where needed your counsel, decide what a signal means and what action follows.

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

Query the Bitcoin blockchain yourself

Pull balances, UTXOs, transactions, on-chain metrics and fund flows from the fully indexed Bitcoin blockchain by REST API, SQL and dashboards. Indexed since 2009, new blocks within seconds, no node to run.

Query the whole Bitcoin blockchain

BitcoinDatabase indexes the public Bitcoin blockchain block by block and returns balances, UTXOs, transactions, on-chain metrics and fund flows by REST API, SQL and dashboards, with no node to run.

REST + SQL + dashboards · indexed since 2009 · new blocks within seconds

Informational on-chain data only · not financial, investment or legal advice · AML features are compliance tooling to support your own review.