# Blockchain Forensics Process: A Step-by-Step Beginner's Guide

> Learn the blockchain forensics process step by step: confirm a transaction, map relevant movements, preserve evidence and understand what the trail cannot prove.

Published: 2026-03-30  |  Updated: 2026-10-02  |  Author: MRHB Network Editorial Team

Canonical: https://mrhb.network/blogs/blockchain-forensics-guide/
See also: https://mrhb.network/llms.txt

---

> **Important:** This article explains public blockchain records for education and victim-support preparation. It is not legal advice, an investigation mandate or a method for identifying, confronting or exposing a person. If money may have been stolen, preserve what you have and use an appropriate law-enforcement, regulator, exchange or fraud-reporting channel in your jurisdiction.

## Quick answer

The **blockchain forensics process** is a structured way to collect, read, map and document blockchain transaction records.

A beginner-friendly process has seven steps:

1. preserve the starting information;
2. identify the correct blockchain network;
3. confirm the transaction in a reliable explorer;
4. read what the transaction actually records;
5. map only the relevant movement;
6. separate facts from labels and assumptions; and
7. save the evidence, limits and next action.

The most important rule is simple: **a transaction trail can show technical movement, but it does not automatically prove who controlled an address, why a transfer happened or whether an act was illegal.**

## What is blockchain forensics?

Blockchain forensics is the examination of blockchain data to understand how a digital asset moved across a network.

The process may use:

- a transaction hash;
- a wallet address;
- the block and timestamp;
- the asset and amount;
- inputs and outputs;
- token transfers or smart-contract events; and
- carefully checked labels supplied by an explorer or analysis service.

NIST describes a blockchain as a distributed ledger designed to be tamper evident and tamper resistant under normal operation. That makes many transaction records useful for review. It does **not** make every explorer label, screenshot, copied dataset or human interpretation correct.

### Transaction mapping in plain English

**Transaction mapping** means following relevant movements from a verified starting point and recording each step.

Imagine a parcel-tracking page. It may show that a parcel moved through three depots. It does not necessarily tell you who personally handled it, why it moved or who legally owns its contents. A blockchain trail has a similar limit: movement is not the same as identity or intent.

## Four terms to understand first

| Term | Plain-English meaning | What it does not prove |
|---|---|---|
| **Transaction hash** | A unique identifier for a transaction on a particular network | Who was behind the transaction |
| **Address** | A public identifier used in blockchain activity | A person's identity or permanent ownership |
| **Block explorer** | A website or tool that displays blockchain records | That every label or decoded detail is complete and current |
| **Confirmation** | Evidence that a transaction has been included in the network's ledger history | That the transfer was lawful, authorised or recoverable |

Always identify the network as well as the hash or address. Similar-looking identifiers can exist on different networks, and using the wrong explorer can produce a false result.

## The blockchain forensics process, step by step

### Step 1: Preserve the starting information

Begin with what you received directly. This might be a transaction hash from a wallet, an exchange receipt or a payment record.

Record:

- the transaction hash;
- the stated network;
- the asset and amount;
- the date, time and timezone;
- the source of the information;
- relevant screenshots or exported records; and
- any messages, domains, usernames or receipts connected to the event.

Keep the original material unchanged where possible. Work from a copy. Do not edit a screenshot and then treat the edited version as the original.

Never share a seed phrase, private key, password or one-time code. A legitimate investigator, exchange or support service does not need those secrets to read a public transaction.

### Step 2: Identify the correct network

The same asset name may appear on more than one network. For example, a token may exist on Ethereum and on another compatible chain. A wallet interface can also display several networks in one place.

Check the receipt, withdrawal record or wallet details for the network name. If it is unclear, stop and ask the relevant provider through an official support route. Do not guess from the address alone.

This step matters because each network has its own explorer, transaction structure, fee asset and confirmation rules.

### Step 3: Confirm the transaction

Open a reputable explorer for the confirmed network and search the complete transaction hash.

Check:

- whether the transaction exists;
- its status;
- block number or height;
- timestamp;
- sending and receiving identifiers;
- asset and amount;
- fee; and
- token transfers or contract events, where relevant.

If the consequence of an error is serious, cross-check the transaction through a second reliable data source or a network node. Record which source you used and when you checked it.

> **Do not search a seed phrase or private key in an explorer.** Only public transaction hashes and addresses belong in public search tools.

### Step 4: Read the transaction model correctly

Not every blockchain records movement in the same way.

#### Bitcoin-style UTXO records

Bitcoin transactions use **unspent transaction outputs**, usually shortened to UTXOs. A transaction consumes one or more earlier outputs and creates new outputs.

One output may be the intended payment. Another may return change to a wallet controlled by the sender. That is why a transaction with two outputs does not automatically represent two separate payments.

#### Account-based records

Ethereum uses an account-based model. A signed transaction changes the network's state and may call a smart contract. One transaction can create several token-transfer or contract-event records.

A simple `from` and `to` view may therefore miss important activity. Check the value transfer, token transfers, contract events and transaction status together.

The official Bitcoin and Ethereum documentation explains these structures in greater technical detail. For a beginner, the practical rule is: **use the model of the network you are examining, not a generic sender-to-recipient assumption.**

### Step 5: Map one relevant movement at a time

Start from the confirmed transaction and follow only the movement connected to your question.

For each step, record:

| Field | Example of what to record |
|---|---|
| Network | Bitcoin, Ethereum or the exact relevant chain |
| Transaction | Complete transaction hash |
| Time | Block timestamp and timezone used in your notes |
| From/to | Address, output or account identifiers as displayed |
| Asset and amount | Exact asset symbol, contract where relevant, and amount |
| Action | Transfer, swap, bridge, contract call or hosted-service deposit |
| Source | Explorer, node or data provider checked |
| Confidence | Confirmed record, probable connection, possible connection or unresolved |

Do not follow every branch merely because it exists. A large graph can look impressive while hiding the absence of a clear question.

Stop when:

- the trail enters a hosted service and the public ledger no longer shows customer-level movement;
- a bridge or swap creates a connection you cannot independently verify;
- a label is the only evidence connecting two events;
- the network or asset is uncertain; or
- the next step would require private, restricted or legally compelled information.

Stopping at an evidence boundary is better than filling the gap with a guess.

### Step 6: Separate facts, labels and inferences

Use three columns in your notes:

| Evidence layer | Example | How to write it |
|---|---|---|
| **Observed fact** | The ledger records an asset transfer from address A to address B | “Transaction X records…” |
| **Third-party label** | An explorer labels address B as belonging to a service | “Explorer Y labelled the address as… on the checked date” |
| **Inference** | Timing and amount suggest a possible continuation | “The pattern may be consistent with…, but alternatives remain” |

An address is not a person. A service deposit address may be shared. A clustering method may group unrelated activity. A label may be stale, incomplete or wrong.

If you cannot explain where a label came from, treat it as an unverified lead—not a fact.

### Step 7: Save a repeatable evidence note

A useful evidence note lets another qualified person understand what you checked.

Include:

1. the question you were trying to answer;
2. the verified starting record;
3. the network and data sources;
4. the date and time of collection;
5. the transaction table or map;
6. which statements are facts, labels or inferences;
7. alternative explanations;
8. where the public trail stops; and
9. the appropriate next action.

NIST's forensic guidance separates collection, examination, analysis and reporting. It also warns that general forensic guidance is not legal advice or a complete investigation manual. Real cases may require management, legal, privacy, compliance or law-enforcement review.

For professional readers who need to combine on-chain evidence with lawful public-source context, the separate [advanced blockchain-forensics and OSINT workflow](https://mrhb.network/blogs/blockchain-forensics-osint/) covers provenance, confidence and reporting in more depth.

## What the process can and cannot tell you

### It may help show

- that a transaction was recorded on a particular network;
- which public identifiers and assets were involved;
- when the network recorded the activity;
- whether a smart contract, bridge or known service address appeared; and
- where the public trail becomes uncertain.

### It does not automatically prove

- the identity of the person controlling an address;
- beneficial or legal ownership;
- why a transfer happened;
- whether a transaction was authorised or criminal;
- that an explorer's label is correct; or
- that assets can be frozen, reversed or recovered.

This distinction protects both the investigation and people who could be wrongly identified.

## What to preserve after a suspected scam

If you are the victim of suspected fraud, focus first on preservation and official reporting.

Save:

- transaction hashes;
- sending and receiving addresses;
- asset names, contract addresses and networks;
- amounts, fees and dates;
- exchange or wallet receipts;
- messages, email headers and usernames;
- website addresses and app names; and
- any report or ticket numbers.

The FBI's IC3 guidance asks United States complainants for these transaction details and warns people to be cautious of recovery services, especially services requesting an up-front fee. Outside the United States, use the relevant police, regulator, exchange or national fraud-reporting route.

Do not confront a suspected person, send more money to “unlock” funds or give anyone wallet secrets. Transaction tracing does not guarantee recovery.

## Common beginner mistakes

### Treating an address as a name

An address shows blockchain activity. It is not a verified identity record.

### Using the wrong explorer

A transaction must be checked on the network where it occurred.

### Following the biggest number

Change outputs, batching, token events and contract calls can make a transaction look different from a simple payment.

### Trusting one label

Service and risk labels are third-party claims. Record their source and check date.

### Assuming “confirmed” means “safe”

Confirmation describes ledger inclusion. It does not certify the recipient, purpose, legality or recoverability.

### Paying a recovery service too quickly

Tracing and recovery are different. Up-front fees, guaranteed recovery and requests for wallet secrets are serious warning signs.

## Frequently asked questions

### Can anyone trace a blockchain transaction?

Anyone can inspect public records on many blockchains. Interpreting complex transfers, labels and evidence limits responsibly may require network-specific and forensic expertise.

### Can a wallet address reveal a person's identity?

Not by itself. A separate, lawful and independently verified source would be needed to support an identity claim.

### Is blockchain data immutable evidence?

NIST describes blockchains as tamper evident and tamper resistant under normal operation. That does not make every explorer page, label, screenshot or interpretation correct. Preserve those items with their source and check date.

### Why can one transaction show several transfers?

A Bitcoin transaction may have several inputs and outputs, including change. An Ethereum transaction may call a contract that produces several token transfers or events.

### Can blockchain forensics recover stolen crypto?

It can help document a public trail. Recovery depends on many separate factors, including control of the assets, provider cooperation, evidence, law and competent authority. There is no guarantee.

## Final takeaway

A useful blockchain-forensics process is careful, narrow and repeatable.

Preserve the starting information. Confirm the network. Read the correct transaction model. Map only the relevant movement. Keep facts separate from labels and assumptions. Record where the evidence stops.

The goal is not to turn a complex graph into a confident accusation. It is to create a clear record that a qualified person can check.