Complete guide to bitcoin transaction analysis: from TXID to blockchain forensics
The public Bitcoin ledger is not just a record of transfers, but a powerful tool for analysis. Any experienced trader or analyst knows: with the right skill, the movement of every single coin can be traced from address to address. An entire industry has been built on this foundation: from tracking whales and exchange inflows to blockchain forensics that recovers stolen assets, and compliance checks for "dirty" coins.
In this article, as the lead analyst at Cryptalist, I will break down the step-by-step process of manual and automated transaction analysis. We will look at basic tools, advanced platforms, and the limits beyond which even the most precise tracing turns into a probabilistic assessment.
Part 1. Manual Analysis: The Foundation Everyone Must Know
Step 1. Finding a transaction by TXID. Every transfer in the blockchain has a unique identifier — TXID. This is a 64-character hash created by the SHA-256 algorithm based on all transaction data. It is impossible to forge: the slightest change in data produces a completely different string. TXID is the "receipt number" by which any network node can find and verify the operation. Finding it is simple: in a wallet or exchange history, there is usually a "View in explorer" link, and if you only have an address, you paste it into the blockchain explorer's search bar, where the entire history is already visible.
Step 2. Transaction structure: inputs, outputs, and change. Bitcoin operates on the UTXO model. Funds are not a single balance, but a set of "banknotes" of different denominations. You cannot spend a "banknote" partially. When paying, it is spent entirely, and in return, two new outputs are created: one for the recipient, and the second — change for the sender — to a fresh address. It is by this feature — a "round" payment versus "fractional" change — that all blockchain forensics is built. Any observer in the explorer can see this structure.
Step 3. Confirmations and the mempool. A transaction does not appear in the blockchain instantly. First, it lands in the mempool — a queue of pending operations. Miners prioritize transactions with high fees. After being included in a block, the first confirmation appears. For small amounts, 1-2 confirmations are enough; for large ones, it is customary to wait for six. The explorer will show in real-time whether the transfer is pending, which block it ended up in, and how much fee the sender paid.
Step 4. Tracing the coin's path. Each input of a new transaction references a specific output of a previous one. Transfers form a branched network. The analyst follows the output addresses, step by step, until a complete chain is formed — all the way back to the coinbase transaction, where the coins first appeared as a block reward. This reveals characteristic routes on the blockchain: a transfer to an exchange, splitting an amount, or withdrawing stolen funds through intermediary wallets.
Part 2. Automation: From APIs to Dashboards
Manual analysis is good for individual cases. But the ledger is updated every second. This is where automation comes to the rescue.
Step 5. Connecting via API. REST APIs of services (e.g., mempool.space) respond to one-off requests: transaction status, address balance. WebSocket APIs maintain a persistent connection and send updates themselves. Blockchair and Bitquery with webhook support are suitable for bulk checks.
Step 6. Automating analytics. Platforms like Dune allow you to write an SQL query once and get a ready-made dashboard that updates itself. Flipside offers a Python-SDK for integration into custom scripts. The key difference: the query is written once, but it works continuously.
Step 7. Monitoring and alerts. A combination of "API plus bot" monitors specific addresses and sends notifications when funds move. Platforms like Arkham offer ready-made alerts for transfers and whale activity. Webhooks are used for custom logic.
Part 3. Blockchain Forensics: The Limits of Probability
Step 8. How forensics works. The basis is address clustering using heuristics. Two key ones: "common input" (if several UTXOs are spent in one transaction, they are controlled by one owner) and "change address identification." On top of this, recognition of typical money laundering schemes is added — splitting amounts or "peeling." Then comes attribution: linking clusters to real exchanges, services, or individuals. This is done by Chainalysis, TRM, Elliptic, as well as open-source engines like GraphSense and BlockSci.
Step 9. Can automation be trusted? Clustering provides a probability, not a fact. Heuristics can be wrong. For example, CoinJoin deliberately combines UTXOs from different users, breaking the common input rule. The risk of leakage can also be reduced manually — the Coin Control function in wallets allows you to choose which UTXO to spend yourself, without mixing coins from different sources.
Bitcoin provides pseudonymity, not anonymity. Persistent analysis often "cracks" it, but the result remains an estimate. As Chainalysis emphasizes, attribution heuristics yield a probabilistic result. A risk assessment is merely a basis for an analyst's decision, not a verdict.
Expert Summary: It makes sense to master on-chain analysis from the bottom up: first the explorer, then APIs and dashboards, and only then specialized tools. The deeper the tracing, the more important it is to distinguish the probable from the proven. In a market where new money laundering schemes and mixers appear daily, understanding these boundaries is a key competitive advantage for an analyst.