Product · Blockchain screening
Assess wallet risk with transaction context.
Bring findings about blockchain addresses into your customer and transaction processes. See which network, data source and relationship type the analysis covers.
The address format does not determine the network; you select it.
Synthetic address; it does not belong to a real wallet.
| Address | Relationship | Label | Direction | Hops | Select |
|---|---|---|---|---|---|
| 0x41a2…c0d8 | Direct | — | Outgoing | 1 | |
| 0x9bf3…77e1 | Direct | — | In / out | 1 | |
| 0x1c6e…a940 | Direct | — | Outgoing | 1 | |
| 0xd05a…3b2f | Direct | — | Incoming | 1 | |
| 0x77c1…e5a9 | Direct | — | Incoming | 1 | |
| 0x2ee4…19bb | Indirect (via A) | — | Incoming | 2 | |
| 0x5f80…6d21 | Indirect (via B) | Mixer service (sample source) | Incoming | 2 | |
| 0xab19…04c7 | Indirect (via C) | — | Outgoing | 2 | |
| 0x63d7…f8e2 | Indirect (via D) | High-risk service category (sample) | Incoming | 2 |
Wallet summary
- Network
- EVM-compatible network (sample)
- Address
- 0x7a3f2c9d41e8b06f5a1c3d7e2b9f4a6c8d0e9c1e
- Risk indicator
- Medium · indirect relationship
- Direct match
- Not found
- Data as of
- 2 Sep 2026 · 09:40 UTC
- Scope
- 2-hop relationship depth · incoming and outgoing transactions
Selection details
How it works
Select the address. Define the scope. Review the result.
-
01
Identify the network and address.
Bear in mind that the same address format can be used on more than one network. When unclear, the user is asked to select the network.
-
02
Start the screening.
Assess the address with the supported analysis type. Query type and relationship depth are defined in the coverage.
-
03
Handle the finding in context.
Review the source and available relationship information together with the customer record.
What a label tells you
A risk label is not enough on its own.
What a label rests on, when it was updated and which relationship it describes all matter. Do not treat a direct record match and indirect exposure as the same result.
The fields of a label · Sample data
- Label
- Mixer service
- Basis
- Sample source · record LBL-3310
- Updated
- 28 Aug 2026 UTC
- Relationship type
- Indirect · 2 hops
- Direction
- Incoming
- Institution action
- Defined in your policy
Moments of use
From onboarding to transfer review.
Wallet assessment
Review the risk information of a new address.
Pre-transfer check
Add the screening result to your institution's decision flow.
Review record
Link the finding to the relevant customer and transaction reference.
Coverage
Network support is explicitly defined.
The same analysis depth may not be available on every network. Review the supported network, query type and data scope before the technical evaluation.
- NetworkSupported network and address format
- Address querySingle-address assessment
- Analysis typeLabel matching, relationship analysis
- Relationship depthHow many hops are followed
- Data scope and limitsSource, freshness, boundaries
Frequently asked questions
About blockchain screening.
Can the network be determined with certainty from the address format?
Not always. Additional network information may be needed, especially on networks that share address formats.
Does a risky label mean automatic blocking?
A screening finding and the action your institution applies are different things. Blocking and review rules are defined in your own policy.
Let's define the flow that fits your needs.
Let's talk about network coverage, analysis type and your integration requirements.