Kin
Also recorded, and not part of the finding above: this picture is on 10 other launches from 11 creator wallets in all, and this creator has 1 other launch 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, 44.4% 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.
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-09-21 20:07 UTC |
| Creator | 91SUeN8wbCG1pDVxbX7H5E3PhxtaAnuoGywc6PHQXFr3 |
| Creator took | 9.8% of supply in the first block |
| Outside buyers | 282 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: 100 within the first 30s, 2 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 | not while we were watching |
| Curve on chain | Nothing to confirm. This launch never reached a graduation threshold while we watched, so there was no completion to check against the curve account. Most tokens end this way, and it is not a finding about them. |
| Creator sold | yes |
| Recorded from | 26v5kuzwgWofdj2Wg9PV2h… slot 449,158,152
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-09-21 20:07:28 UTC Slot 449,158,152, which is the chain's own clock for this moment. |
| Creation block | 2 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 100 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-09-21 20:08:45 UTC +1m 16s
1.477e-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. |
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 11 launches from 11 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 80 launches from 62 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. See this ticker's page → |
| This document | The same launch document, byte for byte, as 1 other launch, across 2 creator wallets in all. See them → |
| This creator | 1 earlier launch, none of which reached a graduation threshold while we watched. See the creator's launches → |
| Files shared with other wallets | Launches by this creator were made with files byte-identical to those of 1 other creator wallet, across 3 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. See the linked wallets → |
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 | Use kin |
| Description | Creator fees go to @usekindotnet, paid through Kin. |
| Metadata held | sha256 8d8492044cfad8b4716a9968a992f479a47b73270dfba3caee9aab2910f10272 · 310 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 48b277db2cd8ef51bc6243f59e49c8dc67b03a923ffb52b261dee75b65f63bf5 · 5,725 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-21 20:07 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.