Launch record · observed at creation 2026-11-10 22:22 UTC
VANAK
vanaK
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-10 22:22 UTC |
| Creator | CaHvYnkMY4BExiE94wgTnUE8QS9HAVLhximJe1e7e8fn |
| 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 | 3 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 | 4oSvim6nfkwKsSwgRBkQHU… slot 467,886,929
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-10 22:22:23 UTC Slot 467,886,929, which is the chain's own clock for this moment. |
| Curve completed | 2026-11-10 22:25:15 UTC +2m 52s Confirmed against the venue's own completion state. |
Times are the blocks' own timestamps, to the second: events in the same block share one, so their order within a block is not shown here.
Seen before
| This picture | No other launch we hold a picture for used this one. |
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 | vanaK |
| Description | 👀 |
| Metadata held | sha256 f900254a6a3240086ddb0f761f3fbb18b277765c93ff6d8c230f3e963c0bc0de · 303 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 8d467936d8ddfa3b7ee1abd55b1135f3ce1f9200836ef2caaa1e5e2c33557830 · 15,390 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-10 22:22 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.