Launch record · observed at creation 2026-11-12 02:28 UTC
USEFUL
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-11-12 02:28 UTC |
| Creator | 3Gjo3LLN37fgG1mXVcF9tfu4f4KGPynbAy9ZjW32m5CJ |
| Creator took | 77.8% 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. |
| Graduated | 1 min after launch |
| Curve on chain | Not read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch. |
| Creator sold | not recorded - this venue's trades do not name the wallet |
| Recorded from | 4mvYWFsbomuWKgqfT2NbvU… slot 468,357,705
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | curve_buyers, unique_buyers, snap30_buyers, bundled_buyers - this launch's venue publishes trade events that do not name the wallet that traded, so no count of people can be taken from them - which is not zero and not a clean result.
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-11-12 02:28:12 UTC Slot 468,357,705, which is the chain's own clock for this moment. |
| Curve completed | 2026-11-12 02:29:27 UTC +1m 15s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-11-12 03:17:13 UTC +49m 01s
2.194e-6 SOL per token.
Reported by a third-party price feed with no trade witnessed, which is a materially weaker claim than a
decoded one.
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 | No other launch we hold a picture for used this one. |
| This ticker | On 494 launches from 361 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 → |
Who took the curve
One transaction bought 80 SOL of this curve, in the same batch of events as the launch, from the creator's own wallet. The wallet and the transaction →
That is the same transaction the token was created in: the launch and the purchase of its float are one signature.
Our launch and trade timestamps are both taken when the events are decoded, so events that arrived together carry the same one. That it was taken at or near launch is on the record; how many seconds after is not.
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 | USEFUL |
| Description | Useful coin here to set levels on useless 🪙 |
| Metadata held | sha256 e8143664c4a231739e34308a93e24e57e42595589039589c11e991a8fec879a1 · 226 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 92f2622545ca5717f3bb0f71fce260b65c849192d95e769012de0da616d8cf7b · 755,455 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-12 02:28 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.