check transaction hash: AML Address and Transaction Analysis
A transaction hash (txid) is the unique identifier that unlocks the complete fund-flow history: from the original source to the final address. check transaction hash instantly establishes whether a specific operation is linked to darknet markets, sanctioned entities, or mixing services. AMLKYC.tech processes txids from all major blockchains and returns a detailed risk report.
What a Transaction Hash Risk Report Contains
A txid report includes: a final score from 0 to 100, a list of risk tags with each source's percentage contribution, chain depth (number of hops to the risky address), and a list of addresses participating in the transaction. Response formats: JSON for automated processing and PDF for the auditor.
Critically: an indirect connection through 3–5 intermediate addresses to a darknet wallet is not a clean result. The algorithm applies risk decay with each hop but does not zero it out completely for significant amounts.
| Risk Level | Score | Recommended Action |
|---|---|---|
| Low | 0–25 | Transaction is safe — document the result |
| Medium | 26–55 | Request source-of-funds documentation |
| High | 56–75 | Escalate to compliance officer, pause payment |
| Critical | 76–100 | Reject transaction, log the incident |
Supported Networks and Data Sources
- Sanctions lists: OFAC SDN, EU, UN, FATF
- Darknet marketplaces and illegal goods platforms
- Mixing services: Tornado Cash, CoinJoin and equivalents
- Unlicensed exchangers and unverified P2P platforms
- Phishing addresses and wallets from compromised protocols
A Bitcoin txid is a 64-character hexadecimal string. An Ethereum txid starts with 0x. For USDT, always specify the network: the same hex hash may exist on both networks with different content and different risk profiles.
Automating check transaction hash via API
The AMLKYC.tech REST API accepts a txid and chain parameter, returning a full JSON report in 1–2 seconds. Batch mode supports up to 100 hashes simultaneously — optimal for auditing a historical transaction archive or processing a withdrawal queue.
Store the JSON response together with the txid in your database: when a regulator or bank requests evidence of screening, you can immediately provide proof with the exact date and result.
Regulatory Context
FATF and national regulators require not just address checks but analysis of specific transactions when disputing payments, handling complaints, and conducting internal investigations. A txid report with the platform's signature is a legally significant document for compliance procedures.
Any address in the transaction matching the OFAC SDN list triggers the "sanctioned entity" tag and requires immediate escalation — this applies to both the sender address and intermediate addresses in the chain.
Practical Use Cases
Incident investigations. When a fraud complaint is received about a specific transaction — immediately request the txid report. It provides the complete fund origin picture for handover to law enforcement.
Historical audit. Batch-checking the archive for a prior period closes gaps in the compliance log before a regulatory inspection.
M&A due diligence. Analyzing key transactions of an acquired crypto platform reveals hidden AML risks before deal closure.
Interpreting check transaction hash Results
- Score 0–25, exchange tag — standard scenario, document and proceed
- Score 26–55, P2P tag — request source-of-funds documentation
- Score 56–75, mixer tag — mandatory manual review, consider filing a SAR
- Any score, OFAC/sanctions tag — immediate escalation to compliance officer
Accessing AMLKYC.tech
Check a transaction hash via the web interface, REST API, Telegram bot, or mobile app. All four channels draw from the same database. Query history is archived for audit purposes. Pricing from $1 per query.
Run check transaction hash Right Now
Enter a txid on AMLKYC.tech — and receive a full transaction risk report in seconds. For high volumes, connect the REST API: from $1 per query with batch pricing for heavy traffic.