Launch record · observed at creation 2026-11-12 16:44 UTC
ZER0
Also recorded, and not part of the finding above: this picture is on 1 other launch. 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. 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-11-12 16:44 UTC |
| Creator | 4aS9j9cg7exwczS2wmECijkvqKfTaL63nox1BJfbwsip |
| Creator took | 0.0% 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 | 8 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 | 5h3Lx6joaxjzCf1WfBBVZz… slot 468,596,666
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. peak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
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 16:44:22 UTC Slot 468,596,666, which is the chain's own clock for this moment. |
| Curve completed | 2026-11-12 16:52:08 UTC +7m 46s Confirmed against the venue's own completion state. |
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 ticker | On 52 launches from 51 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 | ZER0 |
| Description | 0DTE Options on Solana |
| Metadata held | sha256 63f7e6b460bc426531e1e77af2bf330ebe106bc759b8b740af8120acd4d83f09 · 244 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 08ac8fdce3a7f93dde5bb9b3743b02b8cea5bed9ae9258e818b62d116e30c42e · 335,672 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-12 16:44 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.