Flockwatch
Also recorded, and not part of the finding above: this picture is on 2 other launches from 3 creator wallets in all, and this creator has 5 other launches on record. The finding reads this launch's own first blocks; these are about what it has in common with other launches. Both are counts, not findings. Across the archive, 48.1% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.
A record of what this launch was at birth, read from the Solana chain. The transaction it was decoded from is cited below: every figure here can be checked against the chain without trusting us. Not a prediction and not advice.
Cite this record as: Chain of Title, Flockwatch, mint k8ZgTcnw3gmED78kj3PALbuRbAD3iL8LuZjAvC2pump, observed at creation 2026-10-09 22:17 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/k8ZgTcnw3gmED78kj3PALbuRbAD3iL8LuZjAvC2pump
Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.
At launch
| Created | 2026-10-09 22:17 UTC |
| Creator | 9RXDxBsFfxbemUdBxsgjk35yu86wegBiEjgZCwY2VxPd |
| Creator took | 15.2% of supply in the first block |
| Outside buyers | 429 distinct wallets, not counting the creator, bought on the bonding curve - the automatic market a launch starts on, which has to fill up before the token can trade anywhere else: 132 within the first 30s, 14 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together. |
| Graduated | 19 min after launch |
| Curve on chain | Not re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers. |
| Creator sold | yes |
| Recorded from | 4QsS3kZvSngrGP299G1Gs3… slot 455,021,353
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Keep this launch as a document
A dated extract of this one launch, frozen at the moment you buy it: every other launch that carried the byte-identical picture or document, this creator's other launches, and what this register checked. A page you can send to someone, and a clean PDF from your browser's print dialogue.
No account needed; the link arrives by email and is permanent. It is this register's own output, with no signature and no attestation: the scoped, signed version written for a dispute is a provenance report. Everything on this page stays free.
Order of events
| Created | 2026-10-09 22:17:37 UTC Slot 455,021,353, which is the chain's own clock for this moment. |
| Creation block | 14 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 132 distinct buyers, within the first thirty seconds. A snapshot taken off a tick at the thirty-second mark, so
it carries no moment of its own; it is placed here because that is where it happened. |
| Highest price seen | 2026-10-09 22:32:43 UTC +15m 06s
3.322e-7 SOL per token.
Decoded from an on-chain transaction that executed at that price.
A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not
here. |
| Curve completed | 2026-10-09 22:36:14 UTC +18m 37s Confirmed: a PumpSwap pool was found for it. |
Times are receipt times: the moment we decoded the event, not the block's own timestamp. Events that arrived in one batch carry one timestamp, so ordering within a batch is not established, and a second or two here is our latency rather than the chain's.
Seen before
| This picture | On 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 48.1% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 13 launches from 10 creator wallets, including this one. Counted over the launches we watched at birth, the same basis as this ticker's own page, so the two cannot disagree. Across the launches we watched at birth that stated a ticker, 86.9% wear one that more than one creator wallet has launched. See this ticker's page → |
| This document | The same launch document, byte for byte, as 1 other launch, across 2 creator wallets in all. Across the archive, 25% of the launches whose document we hold carry one byte-identical to a different creator's. See them → |
| This creator | 5 earlier launches, 2 confirmed complete on chain. Across the archive, 70.6% of launches come from a creator with more than one launch on record. See the creator's launches → |
| Files shared with other wallets | Launches by this creator were made with files byte-identical to those of 6 other creator wallets, across 8 shared files, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. Across the archive, 58.1% of launches come from a creator linked to at least one other wallet this way. See the linked wallets → |
Pool
| Liquidity | 7.8 SOL |
| Read from chain | 2026-10-10 19:57 UTC, just now |
What this launch claimed to be
| Name | Flockwatch |
| Metadata held | sha256 2cebd26e225f763f3f4a59667a7b3aa79eb2d687677b787b60777f29c10acb54 · 375 bytes Read the document, the bytes themselves rather than our reading of them. The hash above is what the record commits to, so anyone can check the two agree. |
| Picture held | sha256 0cafd799d2f9816cb9ce2e404e980e39c73e04c9a48d26e9fbdcad5a3432c46f · 9,919 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-09 22:17 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.