0.4%of supply taken by the creator in the first block
Noreached a graduation threshold while we watched
215launches carry this ticker, from 115 creator walletsNo finding either wayWe watched this launch and ran the launch-record tests on it: what the creator took in the first block, how many wallets bought on the curve, how fast the curve filled, and whether a single buy completed it. None of them fired, and a marker is one of those tests firing. We still do not head this record 'no markers found': that line is kept for launches whose curve we watched fill slowly with at least thirty outside buyers, and this one did not complete a curve at all. Those tests read this launch's own first blocks only. What it shares with other launches is counted below and is not part of this answer. Neither endorsed nor accused.
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.
noteThe creator sold while we were watching.
At launch
| Created | 2026-09-10 00:08 UTC |
| Creator | A2TgKfpzzQstMJE9d7pH3RSCXnL8G9HegG1xEtpb2oHC |
| Creator took | 0.4% 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, 0 in the very same block the token was created in. |
| 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 | AyMMprHtCZJ5fxettprrMR… slot 445,743,407
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| 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. |
Order of events
| Created | 2026-09-10 00:08:49 UTC Slot 445,743,407, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Highest price seen | 2026-09-10 00:09:15 UTC +26s
3.022e-8 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. |
| 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. |
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 | No other launch we hold a picture for used this one. |
| This ticker | On 215 launches from 115 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 → |
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 | the driving fly |
| Metadata held | sha256 26980af014690e7c3cc64b862c13771e640489f717d7f5e9c84431fc8b5eeace · 233 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 0d45fea68948aed15a18fad1041544b609054423e04d63adf66235d0293d2e38 · 467,536 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-10 00:10 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.