Blue bands
Also recorded, and not part of the finding above: this picture is on 7 other launches, and this creator has 56 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. 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, Blue bands, mint FdJRNonHnXaMLJ6DmteaHGgBdWDd2cKnf9nsj27Cpump, observed at creation 2026-10-25 21:19 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/FdJRNonHnXaMLJ6DmteaHGgBdWDd2cKnf9nsj27Cpump
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-25 21:19 UTC |
| Creator | F24BTBjuqjHtUFYaLA342LUsshUUrPJf31USpvKCrexC |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 14 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: 6 within the first 30s, 0 in the very same block the token was created in. |
| Graduated | 0 min after launch |
| Curve on chain | Not read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch. |
| Creator sold | yes |
| Recorded from | 5dbrgKoRNTb6ETVkKec3qx… slot 461,407,310
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | peak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against
one; it is the record declining to state something. The column names link to their full entries in the
published schema, which is where the rest of the reason is written down. |
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.
Several launches in one matter
A pack of 10 of these documents is $200, redeemed one launch at a time whenever you find the next one. You get a code by email; it does not expire.
Order of events
| Created | 2026-10-25 21:19:10 UTC Slot 461,407,310, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Curve completed | 2026-10-25 21:19:25 UTC +16s Confirmed against the venue's own completion state. |
| Thirty seconds in | 6 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. |
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 ticker | On 15 launches from 4 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, 88.2% wear one that more than one creator wallet has launched. See this ticker's page → |
| This creator | 18 earlier launches. All 2 that reached the graduation threshold on our feed were read on chain, and none had completed. Across the archive, 70.2% of launches come from a creator with more than one launch on record. See the creator's launches → |
Pool
We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.
What this launch claimed to be
| Name | Blue bands |
| Description | runner buy |
| Metadata held | sha256 2701d63b3bd3f9bf12b4946f1b545ff02d4259c50395aff931483829fa2ab3ac · 312 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 0c1afc0ed7ce91e2cf0addb7b76c95d871cf147c5d6cde744f1b2870694fbfb5 · 510,263 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-25 21:19 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.