AI-Powered Detection of Suspicious Blockchain Transactions

We design and deploy artificial intelligence systems: from prototype to production-ready solutions. Our team combines expertise in machine learning, data engineering and MLOps to make AI work not in the lab, but in real business.
Showing 1 of 1All 1566 services
AI-Powered Detection of Suspicious Blockchain Transactions
Complex
~2-4 weeks
Frequently Asked Questions

AI Development Areas

AI Solution Development Stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1317
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1226
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    925
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1156
  • image_logo-advance_0.webp
    B2B Advance company logo design
    620
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    894

AI-Powered Detection of Suspicious Blockchain Transactions

Rule-based AML systems miss up to 30% of suspicious transactions due to evolving money laundering schemes — mixers change algorithms, peel chains become more sophisticated. Our AI system builds a transaction graph and analyzes it in real time using a GraphSAGE/GAT model. Replacing rule-based approaches with GNN provides scalable detection on thousands of transactions per second. We implement it turnkey in 4–8 weeks, adapting the model to your compliance requirements. For instance, on one project we reduced the false positive rate from 12% to 3.1% compared to a rule-based system. Another client saved $80,000 per year by reducing false positives. Additionally, automatic drafting of SARs saved $50,000 in manual review. Typical savings for a mid-size exchange exceed $100,000 annually from reduced false positives and automated SAR drafting.

Blockchain Money Laundering Patterns

Layering through multiple hops — classic money laundering: funds pass through a chain of addresses to break tracing. Our backward tracing algorithm with ML prioritization identifies which addresses in the chain are most suspicious.

Mixer/Tumbler usage — centralized and decentralized mixers (e.g., Tornado Cash) mix transactions for anonymization. Indicators: round amounts, timing patterns characteristic of mixing pools, known mixer addresses. Detection: entity labeling of known mixers plus a behavioral classifier for unknown ones (round amount clustering, pool-like behavior).

Peel chain — a long chain of transactions where each forwards most of the amount to the next address. Typical for withdrawing funds from hacked projects.

Exchange hopping — rapid conversion across several exchanges to obscure the trail. We analyze the cross-exchange transaction graph.

Structuring (smurfing) — splitting large amounts into many small transactions to bypass reporting thresholds. Detection: temporal clustering of transactions from/to one address within a short window.

How the GNN Model Identifies Suspicious Addresses

The transaction graph is a natural environment for GNN. Nodes: addresses. Edges: transactions with attributes (amount, time, type). Task: node classification (addresses) as suspicious/legitimate.

Architecture: GraphSAGE / GAT:

  • Node features: transaction volume, number of incoming/outgoing, average amounts, temporal patterns, age
  • Edge features: amounts, frequency, time windows
  • Aggregation: multi-hop neighborhood information
  • Classification head: binary (suspicious/legitimate) + category (mixer, exchange, scam, etc.)

Training dataset: labeled data from exchange compliance teams + publicly known scam addresses + negative sampling from verified legitimate addresses.

Results on real Ethereum data: precision 0.89, recall 0.82 for high-risk categories. False positive rate: 3.1% on a volume-weighted basis. The GNN model is 3 times more accurate than rule-based systems (precision 0.89 vs 0.4). In speed, GNN processes 50,000+ tx/min, 500 times faster than rule-based (10–100 tx/min).

Why Real-Time Scoring Is Critical for Exchanges

Latency requirement: decision before transaction confirmation (for exchange deposits — upon entry into the mempool).

Architecture:

Mempool monitoring → Feature extraction → GNN inference → Risk decision

Latency breakdown:
  - Mempool to queue: <1s
  - Feature extraction: 50–200ms (graph neighborhood lookup)
  - GNN inference: 20–50ms (ONNX Runtime on GPU)
  - Risk decision + alert: <10ms
Total P99: <500ms

For confirmed transactions (historical): batch processing 10,000+ tx/second.

Speed Comparison

Scenario Throughput Latency P99
Real-time (mempool) 1,000+ tx/min <500ms
Batch (historical) 50,000+ tx/min ~2s per batch

Integration with Regulatory Requirements

FATF Travel Rule (FATF Travel Rule) — for transfers >$1000/$3000, exchanges must transmit sender/receiver information. The AI system automatically:

  • Identifies VASP addresses (Bitfinex, Kraken, etc.) as counterparties
  • Initiates Travel Rule message exchange via TRISA/VerifyVASP protocols
  • Flags transfers to non-compliant addresses

Suspicious Activity Reports (SAR) — upon detecting suspicious patterns, the system auto-drafts an SAR with:

  • Event timeline
  • Amounts and addresses
  • Description of the suspicious pattern
  • Links to known bad actors

The final decision to file an SAR always rests with the compliance officer.

Screening lists — OFAC SDN, EU Sanctions, UN lists — automatic checks on every deposit/withdrawal. Direct and indirect matches via graph analysis.

What the Implementation Includes

  • Audit of current AML system and compliance processes
  • Collection and preparation of a labeled dataset for your blockchains
  • Training the GNN model with hyperparameter tuning
  • Integration via REST API / WebSocket with your platform
  • Documentation (architecture, API, operational instructions)
  • Training of the compliance team on the system
  • 3 months of post-implementation support

How We Implement AI-AML in 4–8 Weeks

  1. Weeks 1–2: Audit and data collection — connect to your blockchain node, load historical transactions.
  2. Weeks 2–3: Dataset preparation — label suspicious addresses, augmentation.
  3. Weeks 3–5: Model training — hyperparameter experiments, validation on your scenarios.
  4. Weeks 5–6: Integration — configure API, WebSocket for real-time stream.
  5. Weeks 7–8: Testing and training — pilot run, threshold tuning, handover of documentation.

Comparison of Rule-Based and AI Approaches

Metric Rule-based AI (GNN)
Precision ~0.4 0.89
Recall ~0.3 0.82
False positive rate (volume-weighted) 12% 3.1%
Speed 10–100 tx/min 50,000+ tx/min

Operational Metrics

  • Coverage: 15+ blockchains simultaneously
  • Processing: 50,000+ transactions/minute
  • Alert volume: 0.3–1.2% of transactions flagged
  • True positive rate among flagged: 68–74% (after ML filtering of rule-based results)
  • SAR auto-draft accuracy: 91% (minimal manual correction by compliance officer)

Request a consultation to evaluate your project. Contact us — together we will implement AI-AML turnkey.