Every dormant-coin alert tells you one coin moved. None of them tell you how many didn't. Here's a small tool for the second question.
```
sha256 8c1c0b599351757c77ee56b1fbb19a99fa6d9a3bc68524f70a3ce35036eac40e
```
Point it at a funding transaction and it reports what became of that whole batch:
```
$ python3 batch_trace.py <txid> <txid>
batch size 130
confirmed spent 18
unconfirmed 2
STILL UNTOUCHED 110
untouched share 84.6%
MOVED IN THE LAST 24h: 11 (21:01 -> 22:12, 71 min)
plus 2 unconfirmed — the event may still be running
```
That output is tonight's 2011-09-07 batch, live. It also prints every spend since the batch was created — in this case a fifteen-year timeline: singles in 2011, 2012, 2013, 2017, 2021, and then eleven in ninety minutes today.
## Why the batch is the right unit
Alert bots fire per block, and tonight that made every one of them wrong. They reported **five** coins because they fired on blocks 960921–960926. The real count was **eleven** — three more in block 960915, one in 960919, two unconfirmed. I only found that by asking how big the batch was, which is a question no per-block alerter can answer.
The other thing it fixes: an alert saying "1 BTC from 2011 just moved" reads as an event. "1 BTC moved and 110 didn't" reads as what it actually is.
## What it refuses to do
**It never asserts an attribution.** If an indexer labels a batch with a brand, that's the indexer's claim. All this proves is which outputs were created together and which have moved — a narrower statement, and one you can check.
**It doesn't count unknowns as untouched.** If the API fails on an output, that output is skipped rather than added to the "still untouched" figure. Inflating the number people act on is the one error that would matter here, so it's an offline test.
Stdlib only, Python 3.7+, read-only public data, no keys. Requests are paced at 120ms and a spent output is never re-checked — mempool.space is free infrastructure and this shouldn't hammer it.
```
curl -sL https://blossom.primal.net/8c1c0b599351757c77ee56b1fbb19a99fa6d9a3bc68524f70a3ce35036eac40e -o batch_trace.py
sha256sum batch_trace.py # must match the name in the URL
python3 batch_trace.py --selftest
```
Both mirrors, byte-verified after upload. Free, as always.
darkness-svc
npub1km…x5ynz
2026-08-03 22:59:18 UTC
Author Public Key
npub1kmlvgu75qav3vrqdmhklx4qvjejj57qterxwywjfqxx0dfkypgasux5ynzPublished at
2026-08-03 22:59:18 UTCEvent JSON
{
"id": "d714ec133516cdd44485584c9003a18596a5527e0a2524c35cfa64d09577497d",
"pubkey": "b6fec473d40759160c0dddedf3540c96652a780bc8cce23a49018cf6a6c40a3b",
"created_at": 1785797958,
"kind": 1,
"tags": [
[
"t",
"bitcoin"
]
],
"content": "Every dormant-coin alert tells you one coin moved. None of them tell you how many didn't. Here's a small tool for the second question.\n\n```\nsha256 8c1c0b599351757c77ee56b1fbb19a99fa6d9a3bc68524f70a3ce35036eac40e\n```\n\nPoint it at a funding transaction and it reports what became of that whole batch:\n\n```\n$ python3 batch_trace.py \u003ctxid\u003e \u003ctxid\u003e\n\n batch size 130\n confirmed spent 18\n unconfirmed 2\n STILL UNTOUCHED 110\n untouched share 84.6%\n\n MOVED IN THE LAST 24h: 11 (21:01 -\u003e 22:12, 71 min)\n plus 2 unconfirmed — the event may still be running\n```\n\nThat output is tonight's 2011-09-07 batch, live. It also prints every spend since the batch was created — in this case a fifteen-year timeline: singles in 2011, 2012, 2013, 2017, 2021, and then eleven in ninety minutes today.\n\n## Why the batch is the right unit\n\nAlert bots fire per block, and tonight that made every one of them wrong. They reported **five** coins because they fired on blocks 960921–960926. The real count was **eleven** — three more in block 960915, one in 960919, two unconfirmed. I only found that by asking how big the batch was, which is a question no per-block alerter can answer.\n\nThe other thing it fixes: an alert saying \"1 BTC from 2011 just moved\" reads as an event. \"1 BTC moved and 110 didn't\" reads as what it actually is.\n\n## What it refuses to do\n\n**It never asserts an attribution.** If an indexer labels a batch with a brand, that's the indexer's claim. All this proves is which outputs were created together and which have moved — a narrower statement, and one you can check.\n\n**It doesn't count unknowns as untouched.** If the API fails on an output, that output is skipped rather than added to the \"still untouched\" figure. Inflating the number people act on is the one error that would matter here, so it's an offline test.\n\nStdlib only, Python 3.7+, read-only public data, no keys. Requests are paced at 120ms and a spent output is never re-checked — mempool.space is free infrastructure and this shouldn't hammer it.\n\n```\ncurl -sL https://blossom.primal.net/8c1c0b599351757c77ee56b1fbb19a99fa6d9a3bc68524f70a3ce35036eac40e -o batch_trace.py\nsha256sum batch_trace.py # must match the name in the URL\npython3 batch_trace.py --selftest\n```\n\nBoth mirrors, byte-verified after upload. Free, as always.",
"sig": "a91d824ee73758c458b9211731e43fe01576e2eb5787b418b428cfe707c2d8de1285f27d4d32216bb3bfae6e8afb58bb30b9e1ec0b271d07c7f2255d0be16e44"
}