NEW REPORT: $187.75B in high-risk exposure across 99 crypto exchanges
Explore the findings
Skip to content

Blockchain Data Analytics for Crypto Asset Compliance

How compliance teams use on-chain data to screen wallets, monitor transactions, and build evidence for investigations
Anastasiia Kryzhanovska

Anastasiia Kryzhanovska

Senior Content Manager. Crypto & Blockchain Expert

November 16, 2026 12 min read

When a wallet gets a new risk label, the compliance team has to decide which past transfers to review. Blockchain data analytics helps analysts find those transfers by tracing links to the wallet, including links through other addresses.

Once analysts find a link to the flagged wallet, they can check why it was flagged and how the funds moved. If the link appears before a withdrawal goes out, those checks can help the team decide whether to pause it. If it surfaces later, they can help the team decide which past transfers need further review.

Read on to see how blockchain analytics supports these decisions and what evidence to verify before acting on a finding.

Key Takeaways
  • Blockchain data analytics indexes public transactions and adds information about the addresses involved so teams can review transfers in context.

  • Screening checks individual wallets or transfers, while monitoring can flag a pattern across transfers that each passed screening on its own.

  • Compliance teams can verify on-chain transfers and should check the source of wallet labels. Linking pooled funds to a particular customer may require records from the service.

  • Record the rule or tracing method, the date and source of wallet labels, and any coverage gaps so another analyst can review the finding.

See how far high-risk exposure travels before it reaches centralized exchanges in the Global Ledger High-Risk Benchmark.
Explore the benchmark

What Is Blockchain Data Analytics?

Blockchain data analytics is the practice of examining on-chain records to trace asset movements and find patterns across transactions.

A transfer record can show how much moved, when it moved, and which addresses were involved. Blockchain analytics tools give compliance teams more context about those addresses, for example by linking one to a known service.

When a destination address is linked to a risky service, its label can trigger a review before a withdrawal goes out. If the label was added later, the team can check earlier transfers for the same link.

Looking across those transfers can reveal whether a payment was part of a broader pattern, such as repeated withdrawals to the same destination.

If that pattern warrants a closer look, blockchain analytics can help trace those payments through intermediary addresses. How far analysts can follow the funds depends on which transfers the platform captures.

How Does Blockchain Data Analytics Work?

To follow funds through several addresses, a platform first has to identify the individual transfers that connect them.

  1. Collect and normalize on-chain data. A token transfer may be recorded in a smart contract event, so the platform reads those events alongside transaction records. It organizes the resulting transfer records by chain and asset so analysts can search and compare them.
  2. Group and label the addresses in those records. The platform can group addresses that appear to be under common control, then use available evidence to identify a service or risk category. An official sanctions list may identify a specific address. A scam label for a group of addresses may rely on victim reports and evidence linking the addresses.
  3. Analyze the transfers using those labels. The platform can show where a route passes through a known service. It can also flag patterns across transfers, such as repeated payments to a high-risk address.
  4. Review the evidence behind the finding. The analyst checks the transfers and the sources of the labels, then compares the activity with customer records where needed. That gives the team a basis for deciding whether the finding needs more evidence.

How Compliance Teams Use Blockchain Analytics

In blockchain analytics for crypto asset compliance, the same transfer records and wallet labels can inform different decisions. What the team needs to know depends on whether it is assessing a counterparty, reviewing a transfer, monitoring activity over time, or investigating an alert.

Use case What the analysis adds What the team does with it
Wallet and counterparty screening Address and entity labels, direct and indirect links to known risk sources Check the label against its source and review relevant customer or counterparty information.
Screening before funds are released The source of an incoming deposit or the destination of a proposed withdrawal Apply the institution's acceptance or escalation policy before crediting or sending funds, where the workflow allows.
Ongoing transaction monitoring Changes in amounts, frequency, destinations, or exposure across multiple transfers Compare activity with expected behavior, tune rules, and investigate alerts.
Investigations and lookbacks A timeline of transfers and historical links that become visible after a label update Reconstruct the path, identify gaps, and document findings for escalation or reporting.

For example, an ongoing monitoring rule can flag a series of withdrawals to the same address even when each falls below the threshold for a single transfer. The ledger can confirm where the payments went and how often they occurred. If the alert also links the destination to a high-risk service, the analyst needs to check the evidence behind that label.

Read More

Pre-Transaction Crypto Compliance: How Far Should You Trace Before Accepting Funds?

When tracing is enough to credit a deposit, when to escalate, and what evidence to record.
Read the article

Where Blockchain Data Analysis Needs Corroboration

When a monitoring alert links the destination to a high-risk service, the analyst needs to check whether the label applies to the destination address itself or to a wider cluster. If the review also needs to establish which customer initiated the payments, the analyst can match the transfers against internal account records.

Situation What to verify
Uncertain wallet label Check who supplied it, when it was last updated, and whether it applies to the exact address or a wider cluster.
Pooled custodian Use the service's account records where available to check whether an incoming deposit relates to a later withdrawal.
Swap or bridge Match relevant contract events and amounts. Check how the provider counts hops across those events.
Funds combined in one wallet Check balances, other inflows, and the allocation rule behind any exposure figure.
Unsupported chain or asset Record the coverage gap and check whether another data source can resolve it.

A missing label can also leave a gap. In the Ghost Clusters study, researchers compared a commercial provider’s labels with known addresses from three seized illicit services. The provider correctly identified between 24.54% and 94.85% of the known addresses, depending on the service. The study reported fewer than 0.5% false positives and found that coverage changed over time. For some of the services studied, the provider mislabeled few addresses and still missed many that belonged to the service.

When a label does identify a risk source along a route, the analyst still has to establish how much of the deposit can be traced to it. That depends on what happened to the funds at each step.

Worked Example: Assessing Indirect Exposure

A deposit has direct exposure when it comes from an address attributed to a risk source. When the link runs through one or more intermediaries, the exposure is indirect. The analyst then needs to establish how much of the deposit can be traced back to that source.

Consider two hypothetical deposits of 10,000 USDT at Exchange X on Tron.

In each case, a graph places a potential risk source five hops from the exchange when addresses belonging to the same service count as one entity. A hop is one step between addresses or entities. With the deposit amount, network, and hop count held constant, the comparison comes down to what the records show about the source and the movement of funds.

Example A: Funds From a Sanctions-Listed Address

An address on an official sanctions list sends 4,000 USDT through three wallets to a fourth. Each of the first three wallets starts with a zero balance and forwards the full amount without receiving other funds. The fourth wallet also starts empty. It receives the 4,000 USDT and another 6,000 USDT from an unlabeled address, then sends all 10,000 USDT to Exchange X.

Example A. Four intermediaries connect the sanctions-listed address to Exchange X.

Example B: Matching Transfers Through a Pooled Wallet

An address linked to a suspected scam through victim reports and behavioral heuristics sends 10,000 USDT through two wallets to Service C’s deposit address. Service C moves the deposit into a hot wallet shared by its customers. Two hours later, the hot wallet sends 10,000 USDT to another wallet, which forwards it to Exchange X.

Example B. The link between the deposit into Service C and its later withdrawal is unverified.

What the Two Routes Establish

In Example A, the first three wallets forward only the funds from the listed address.

The fourth wallet combines those funds with another 6,000 USDT and sends its entire balance to Exchange X. That supports tracing 4,000 USDT, or 40% of the deposit, to the listed address. The source of the other 6,000 USDT remains unknown beyond the unlabeled sender.

The full-balance transfer is what makes that calculation straightforward. If the fourth wallet had sent only 5,000 USDT, the result would depend on the allocation rule. A proportional rule would assign 40% of that transfer, or 2,000 USDT, to the listed source. A first-in, first-out rule would assign 4,000 USDT if the listed funds arrived first.

In Example B, the ledger shows the deposit into Service C and a later withdrawal of the same amount.

The amount and timing leave open whether Service C credited the deposit and debited the withdrawal to the same customer account. Counting by entity puts the deposit address and the hot wallet at one point on the graph, giving the apparent route five hops. A tool that stops at known services would trace two hops back from Exchange X to Service C.

The share of the Exchange X deposit linked to the suspected scam remains unknown.

Finding Example A Example B
Source label Address on an official sanctions list Suspected scam cluster based on victim reports and behavioral heuristics
Amount linked to the risk source 4,000 USDT, or 40% of the deposit Unknown without evidence connecting the transfers through Service C
Next evidence to request Source of the other 6,000 USDT if relevant to the review Service C records identifying the accounts behind the incoming deposit and outgoing withdrawal

In both cases, five hops describes the distance shown on the graph. What the analyst can attribute depends on the evidence at each step.

At market scale, the Global Ledger High-Risk Benchmark used five hops as its tracing limit when comparing exposure across 99 centralized exchanges from 2021 to 2025. Within that window, sanctions exposure in 2025 averaged 3.06 value-weighted hops, compared with 1.80 for hacks. 

For an individual case, record the tracing limit alongside the finding it supports. In Example A, that means documenting the transfers behind the 40% figure. In Example B, it means recording where the link becomes uncertain and which Service C records could resolve it.

Read More

AML Risk Scoring for Crypto: How to Score Transactions Using Exposure, Asset and Blockchain Distance

How exposure, source category, asset and blockchain distance feed into a transaction risk assessment.
Read the article

Checklist: What to Document in a Compliance Review

A case record should let another analyst pick up the review without repeating the work. Start with what triggered it, then document the evidence behind the decision and any open requests.

  • Transaction details. Record the transaction hash, asset, network, amount, and timestamp. Include the internal account or case reference if you can link it to the transfer.

  • Reason for review. Record what triggered the review, such as a screening hit, a monitoring alert, or a new wallet label. For a monitoring alert, save the rule version and the transfers that triggered it.

  • Wallet labels. Save the source and date of each label that affected the finding. Note whether it applies to a specific address or to a group of addresses believed to be under common control.

  • Tracing method. Record where the trace started, which direction it followed, the hop limit, and where the trace stopped. Note whether you counted hops by address or by entity. If you estimated an exposed amount, include the allocation rule and the figures you used.

  • Findings and evidence gaps. Separate verified transfers from inferred links and record any gaps in coverage. For a pooled service, specify which account records could show whether a deposit and a later withdrawal involved the same customer.

  • Decision and follow-up. Record what the team decided and which evidence supported the decision. Assign an owner to any outstanding request and note what information would warrant reopening the case.

When new evidence arrives, add it as a dated update to the case file. Identify which finding it affects and record whether the team changed its decision.

Conclusion

Blockchain data analytics helps compliance teams screen pending transfers, spot patterns across transactions, and trace funds when an alert warrants investigation. How much a team can conclude depends on the transfers it can verify and the evidence behind the wallet labels. A clear case record lets another analyst reassess the finding when a label changes or a service provides new account records.

Global Ledger KYT lets teams review the source and use of funds behind an alert in the same workflow they use to screen wallets and monitor transactions.

Back your crypto compliance decisions
with on-chain evidence
Schedule a demo

FAQ

Why can two blockchain analytics tools flag different exposure for the same transaction?
Tools can use different labels, chain and asset coverage, hop limits, and allocation rules. Check the data and method behind each result before treating the figures as comparable.
Can blockchain analytics identify who owns an unhosted wallet?
Identifying the person behind an unhosted wallet generally requires off-chain evidence such as verified customer records. A signed message can demonstrate control of an address, while identifying the person who signed it requires additional evidence.
Can analysts reproduce a finding after wallet labels change?
They can reproduce it if they can recover the original data, labels, and method. If the earlier label is unavailable, the case record can still show what the analyst relied on at the time.