Also recorded, and not part of the finding above: this picture is on 1,167 other launches from 12 creator wallets in all, and this creator has 3,747 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, 56.3% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.
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 12:33 UTC |
| Creator | DGdAKTVXQS1xESMkUkK1DwzUfwEYwvFckw6At4jbbaQr |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 0 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: 1 within the first 30s, 0 in the very same block the token was created in. |
| Graduated | 4 min after launch |
| Curve on chain | Incomplete. We read the bonding curve account 61.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. |
Order of events
| Created | 2026-09-02 12:33:23 UTC |
| Creation block | No wallet bought in the block the token was created in. |
| Thirty seconds in | 1 distinct buyer, 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 12:37:33 UTC +4m 11s 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 12:37:58 UTC +4m 35s
1.363e-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 1,168 launches from 12 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.3% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 456 launches from 286 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, 89.5% wear one that more than one creator wallet has launched. See this ticker's page → |
| This creator | 3,747 earlier launches, 1 confirmed complete on chain. Across the archive, 70.7% 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 2 other creator wallets, across 4 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, 63.9% 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 | p |
| Metadata held | sha256 32d299af23a79d1aa6396a89273e8400e5014cc11c5782b5f91ea0473d9c8695 · 284 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 42014e1f0b40306a7e0d1c956f9da803eb06568ea4be499248afc3e6cb3319bc · 14,328 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-10 20:02 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.