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-03 06:43 UTC |
| Creator | AyQC5vYEEpCvTjjNDAA1X9aSDWEB7AqT4iakMfXQpAqu |
| Creator took | 3.4% of supply in the first block |
| Outside buyers | 7 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: 0 within the first 30s, 0 in the very same block the token was created in. |
| Graduated | 4.6 h after launch |
| Curve on chain | Incomplete. We read the bonding curve account 61.6 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 06:59 UTC. |
| Creator sold | not while we watched |
| Recorded from | 3MYq9gsGF4HHwAUhdxBnb4… slot 443,905,372
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-03 06:43:11 UTC Slot 443,905,372, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Thirty seconds in | No 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. |
| Highest price seen | 2026-09-03 07:14:26 UTC +31m 14s
3.329e-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. |
| Curve completed | 2026-09-03 11:21:17 UTC +4h 38m 05s 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. |
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 210 launches from 160 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 | Risk Callout |
| Description | Risk Callout. The microphone is on, the call is outside. You make the decision. |
| Metadata held | sha256 d97fec8d47ba356ad48244695bf59fb1bca0ebe5727459c469a0e5c5931ffb95 · 340 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 d49c9951537e06cd75df022f2c16d531bac8937f2f21c2b0509c56ff92b45409 · 1,237,136 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-12 04:22 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.