lm
Also recorded, and not part of the finding above: this picture is on 189 other launches from 2 creator wallets in all, and this creator has 522 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, 46.5% 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. We did not record its creation transaction, so these figures rest on our observation at the time rather than on a citation you can follow. 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-02 14:57 UTC |
| Creator | DwZguksR52vhH3xjktZFgPvXs2LiqrBLpnRZbEdd7DyB |
| Creator took | 0.3% of supply in the first block |
| Outside buyers | unknown 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: 3 within the first 30s, 1 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 | 1 min after launch |
| Curve on chain | Incomplete. We read the bonding curve account 24.9 days ago and it had not finished, though a graduation event was recorded for it. This launch is not counted as a graduation anywhere on this site. Checked 2026-09-11 23:42 UTC. |
| Creator sold | yes |
| Recorded from | Not recorded. This launch predates our keeping the creation transaction (2026-09-09), and its trade rows had been pruned by retention before the backfill could recover the signature from them. The figures above stand on our own observation alone, which is weaker than a citation, and we would rather say so than leave the gap unmarked. |
| Not recorded | curve_buyers - its trade rows had already been sampled at finalize or pruned by retention before anything counted them, so any count over the survivors would be a floor rather than a measurement.
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.
Order of events
| Created | 2026-09-02 14:57:37 UTC |
| Creation block | 1 wallet bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 3 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. |
| Curve completed | 2026-09-02 14:58:42 UTC +1m 04s Not confirmed. An inference from decoded trade volume that nobody ever confirmed, and where the curve
account has since been read, the great majority of those returned incomplete. |
| Highest price seen | 2026-09-02 15:00:56 UTC +3m 19s
2.892e-7 SOL per token.
Source not recorded, which is every row written before 2026-09-10 - never that the peak was
unsourced.
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 190 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 46.5% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 357 launches from 56 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.4% 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 37 other launches, all of them this same creator's. Across the archive, 11.3% of the launches whose document we hold carry one only their own creator reused. See them → |
| This creator | 522 earlier launches. 67 reached the graduation threshold on our feed; we have read the curve account for 63, and 63 had not completed. Across the archive, 71.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 1 other creator wallet, across 2 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, 57.8% of launches come from a creator linked to at least one other wallet this way. 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 | LION MUSK |
| Metadata held | sha256 05f768171e32991d31cef0b73308995e29c9f1feaadf3a335445157aa23691cb 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 b68b8acd20253704b18d9e9e1997ff8e7a29b1f20bdc829991115a707f5d77fd · 72,234 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-10 21:18 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.