Skip to content

Samples

thaneye edited this page Nov 13, 2026 · 3 revisions

Samples

Under the search box the front page has a block No address at hand? Start from an example, with a link Open a saved workspace beside its heading. Each card says what to look for and what the example does not show. A prepared example opens a canvas that is inside the link itself: nothing is looked up, so it opens at once and works without a data source. The canvas is an ordinary one: select, expand, label and export as in any other. The card for a real wallet says so when it looks the wallet up live.

The first two cards are always in view. When two or more follow them, the page folds those under a line More examples (N), grouped under small headings; it opens with a click or the keyboard, and a link ending in #examples opens it. The start page remembers nothing, so it begins folded every time.

A plain transaction

What it is. A real payment from 5 April 2022 (block 730576): transaction 35a8e48ecf210d2b5d86ff88c02a5d6f41038b0ed9ef639d97bde16c4261d2fd, one input, two outputs and a fee. It was chosen because it shows no pattern and Hopline's change guess is clear, not because of who made it: nothing is known or claimed about the people behind it.

Walk through it.

  1. Open it from the front page. The canvas shows four vertices in the Flow layout: Spent from here, the transaction A plain payment, and two outputs, Likely the payment and Likely the change. The four labels and the note on the transaction were added to the example; the amounts and the rest come from the chain.
  2. Inputs, outputs and the fee. The wallet spends one coin of 0.02522100 BTC. The outputs are 0.00900000 BTC and 0.01578900 BTC. What is left, 0.00043200 BTC, is the fee: no output receives it, and inputs = outputs + fee.
  3. The change. The amber line goes to the output Hopline takes to be the change, 0.01578900 BTC. Select the transaction and read Likely change in its details: it gives the two reasons (the only output of the same address type as the input, and the other output is a round amount while this one is not) and a confidence (high).
  4. What it does not show. Who owns any of the wallets. The change is a guess from the shape of the transaction: a wallet that pays a round amount to a wallet of its own type, or one that does not use fresh change addresses, can fool it. That is why it says likely, and why it is one of the Change guesses in the Findings and not a finding.
  5. Go on. Add the transaction's id in the Add box to load it from your data source and see what Hopline then knows (the earlier transaction that funded the sender, and whether each output has been spent), then press Show backward or Show forward.

How it was made. The canvas link was built from the transaction as a public explorer returns it. The earlier transaction that funded the sender was left out of the picture so that it shows one input and two outputs, and four labels and a short note were added.

Why not the 2010 pizza purchase or the first transactions? They are famous, but they are not plain. The pizza payment spends 131 coins of one address in a single output of exactly 10,000 BTC, with no change: a consolidation (it shows CONSOL 131→1). The first payment between two people (block 170, January 2009) pays to bare public keys, which Hopline draws as non-standard outputs, and its change of 40 BTC is a round amount. Both teach something else and may become examples of their own.

A real case: the Colonial Pipeline ransom wallet

What it is. A wallet with a short history that received the DarkSide affiliate's share of the Colonial Pipeline ransom in 2021. Unlike the plain transaction, this card opens the wallet overview and looks the wallet up live from your data source.

Look for how the coins arrived and where they went, transaction by transaction, in the wallet's ledger, and use Open in workspace to follow them.

It does not show who is behind the wallet: that comes from public reporting, not from the chain.

A consolidation

What it is. A real transaction from 21 January 2021, 0a097ace51cd19f90d8345ead061cf5cc2ade17556025ab7df8487b1e54e4d4d: eight inputs from eight wallets gathered into one output of 0.20092093 BTC.

Walk through it. The canvas shows all of it: the eight wallets on the left, the transaction with its CONSOL 8→1 badge, and the one output. The dashed ring round the eight wallets is the common-input rule: wallets spent together are probably one owner, so Hopline groups them (a Clusters count in the Findings). There is no change: everything went to one place.

It does not show who the owner is. The rule can be wrong: a CoinJoin or a wallet shared by several people breaks it. Compare the next example.

A CoinJoin

What it is. A real transaction from 18 May 2026, 6a756922c594fe58d8cc54ee475e81fa5d4833c4c3c3f40f6e64c7093cfd5d57: 18 inputs from 18 different wallets and 19 outputs, ten of them exactly 0.00547856 BTC.

Walk through it. The whole transaction is on the canvas. The pink COINJOIN? badge says it looks like a CoinJoin: several wallets' inputs and several outputs of the same amount. Unlike the consolidation, the input wallets are not grouped, because wallets spent together in a CoinJoin are probably different owners. Select the transaction to read the reason.

It does not show which output belongs to which input, or who took part: the equal outputs cannot be told apart, and the chain cannot prove that this is a CoinJoin and not some other batch of equal payments.

A peel chain: the same amount, again and again

What it is. A run of 25 real transactions on 4 March 2024 (19:12 to 21:50 UTC), starting with 5c15e4945e11a04555275795d488a27e7f513f4f419198c5230404b4881689fc. Each has one input and two outputs: exactly 1 BTC to the same wallet, and the rest passed on to the next transaction. The first 12 are shown.

Walk through it. The coin runs along the straight line in the middle, each step labelled PEEL 1/12 to 12/12, with the amount on the line shrinking by 1 BTC each time. Every payment is peeled off upward, and all twelve land in one wallet (the 1 BTC lines fanning into it). Hopline marks each step ROUND 1 BTC too, since the payment is a round amount.

It does not show who owns any of the wallets or why this was done. Ordinary wallets that pay out of one coin look the same. The receiving wallet has over 10,000 transactions, so it may be a service rather than one person, and the run ends there: it later spends coins in larger batches (one of them 26 inputs), mixed with others.

A peel chain that may be a service paying out

What it is. A real run of ten transactions on 3 March 2020, starting with 319b242430e7e00782a56496ed8ee253d0f839f7128973dc34c8b9272b395524: a coin of about 75 BTC pays a small amount at each step and passes the rest on. Hopline marks it PEEL 1/10 to 10/10.

Walk through it. It has the same shape as the previous example, but look at the numbers: under half a percent of the coin is peeled in all, and all ten transactions happen on the same day.

It does not show whether a person or a service did this. A service paying out many customers from one large coin has the same shape; only more evidence, such as who the wallets are and what the payments were for, can tell them apart. That is why Hopline calls it a possible peel chain.

Where a trail meets an exchange

What it is. A real deposit from 1 February 2023, 42c404ad990d5c1f0889e3506198430e256f23975a7e020cb31b44c0b1a782c1: 4.2076562 BTC go to 1VERF5rDyVoS4mPCbK68vSGpVo95cAXRm, a wallet that Hopline's built-in list names Gemini Hot Wallet, and 0.10807976 BTC come back as change.

Walk through it. The trace starts at the depositor. The named wallet is drawn as a green hexagon with the EXCH tag: EXCH is Hopline's tag for an exchange, and it marks the wallet as a service. (A wallet that a list names as an exchange gets this tag by itself when you load it into a trace; here it is already set in the canvas.) Because it is a service, Hopline follows a trail until it meets one, and the Findings count Service hand-offs 1. Open the Service hand-offs list to see it, and select the named wallet to see the list's name and where it comes from.

It does not show what the exchange did next: its wallets pool many people's coins, so the trail stops being about one person there. The name is a claim from a list, not proof.

How these were made. Each canvas was built from the transactions as a public explorer returns them, with the transactions that funded the first wallet left out and a few labels and notes added. The peel runs are laid out as a straight line with the payments peeled upward, because the default layout draws a run like this as a tangle. All of them are ordinary canvases: select, expand, label and export as in any other.

A batch payment

What it is. A real transaction from 16 November 2021, 2ce0377b41ca82a4709f3a6a176d917cdbd2285d353a22365bace58f9a90cdc9: one input of 0.29797486 BTC paying 12 different wallets in one transaction, with amounts from 0.0009 to 0.27 BTC.

Walk through it. The whole transaction is on the canvas: the paying wallet, the transaction with its BATCH 1→12 badge, and the twelve recipients fanning out, each line labelled with its amount. Compare the CoinJoin: many outputs there too, but several payers.

It does not show who is paying or being paid. A batch like this is typical of an exchange or service paying many people at once, but a payroll or a payout run looks the same.

A payment that asks to be swapped

What it is. A real transaction from 18 October 2026, e045a10b4512aad52e7f70bab09bd0ca031992b23a99268bd6cf6615c2fecebe: one input of 0.0006348 BTC, a payment of 0.00026004 BTC, 0.00036848 BTC back as change, and a third output, an OP_RETURN, that holds a memo.

Walk through it. Hopline reads the memo as a THORChain swap memo and marks the transaction SWAP → E (the E is a short code for the asset the payment is to be swapped into). Select the transaction to read what the memo asks for: the asset, the address on the other chain it is to be paid out to, a limit and an affiliate. The grey vertex on the canvas is the memo output. The payment goes to a wallet with hundreds of transactions and over a thousand bitcoin received, which is how a swap service takes deposits. All of the transaction is in the example, the memo output included: a pattern can only be read from a whole transaction.

It does not show that the swap happened: the memo is what the sender wrote, and a swap that cannot be done is refunded. What happens on the other chain is not on this one, so the next step of a trail like this is to follow the address in the memo there.

A wallet a security vendor lists for a ransomware group

What it is. The wallet bc1q0wf73xmcqkvrvs7tj49hznxqqgt6tp359gk0az, which the WatchGuard Technologies ransomware tracker lists among the wallets of the Dark Angels group. Four real transactions, May and June 2022: a tiny first payment of 0.00012345 BTC; then exactly 38.14 BTC in one payment (the tracker gives 38.14 BTC as one of the group's extortion amounts); twenty minutes later the 38.14 BTC leave in two pieces, 6.356666 BTC and 31.783321 BTC (one sixth and five sixths); and on 23 June the leftover 0.00012345 BTC is spent together with 6.356623 BTC from another wallet.

Walk through it. The wallet carries the name Dark Angels wallet, per WatchGuard and Hopline's red THREAT tag, so it is the reference for routes (the Route to part of the other vertices is measured from it). The ROUND 38.14 BTC badge is on the payment. Select the wallet to read the note, which names the source.

It does not show who paid, or who controls the wallet. The name and the tag are WatchGuard's claim, taken from its page; the chain shows only the amounts and where the coins went. The page names no transaction and no victim: the example is matched on the address and on the amount, which is not proof that any person paid a ransom. Hopline links to the page and does not copy it; it is WatchGuard's.

More examples can be added the same way: the first two cards stay in view and the rest fold under More examples.

Clone this wiki locally