Follow 55 BTC through one spend

At 11:21:16 UTC on March 4, 2014, a Bitcoin transaction created an output of 55 BTC to 16KPSUWhYbHxjAmdLH1wuTq3evFy1MRJ7m. At 03:29:12 UTC on March 6, another transaction consumed that output. The elapsed time was 40 hours, 7 minutes, 56 seconds, using the two blocks’ timestamps.

Inspect the original output or open the address timeline.

First, establish what was created

The funding transaction is 8581990e5dab42669db6f43f1ccc3f95d9a19c172dbfed40eba05d89d032b7f5, included in block 288,863. Its two inputs supplied 66.56863031 BTC. It created these outputs:

The difference is the fee: 0.00010000 BTC, or 10,000 satoshis. Output numbers start at zero, so the 55 BTC output is output 1.

Then check the spending input

The spending transaction is 2ab9d01e34bc302b17c5726926b05ff1b30bc9dcd1b9c5048dfa31f686dd2375, in block 289,125. Its only input explicitly references the funding transaction and output 1. The previous output’s amount and script agree with the saved funding record. This is a direct transaction relationship; an address appearing in both records would be weaker evidence.

The new transaction created 54.98877317 BTC at 1AuJeHabgXBEvRTaLdnL7Gi8UpPj1QuKRc and 0.01102683 BTC at 1GZRMGxHNFo4HNieyJvTs3Guj7AUhDLetR. Their sum is 54.99980000 BTC. Adding the 0.00020000 BTC fee reconciles exactly to the original 55 BTC.

What this proves, and what it leaves open

The records support the claim that this output was consumed by this transaction. They do not identify the people involved, explain why it was spent, or tell us which new output was payment versus change. The larger output is not automatically the payment. Block timestamps are also not exact observations of when a person pressed Send.

This page follows one output through one spend. It does not claim to have established the later history of either new output, or the full activity of a wallet.

Keep and inspect the evidence

Download the funding transaction, spend observation, spending transaction, and source and hash manifest. These files remain with this edition even after the live lookup cache expires.

The source observations came from Blockstream’s public Esplora API: funding, output spend, and spending transaction. The Esplora API specification describes the fields. ztrash checks their consistency; this edition does not include an independent full-node verification or a Merkle inclusion proof.

Edition 1 · September 26, 2026 (Pacific). These are explanations of public provider observations, not identity findings. Each evidence bundle records its UTC collection time and file hashes. Corrections should identify the transaction, disputed statement, and supporting source; use the Support link in the site footer. Material corrections will be recorded in a new edition while retaining this evidence bundle.