Launch record · observed at creation 2026-11-12 09:35 UTC
NOSKCAJ
noskcaJ
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 09:35 UTC |
| Creator | Hb2nYo8dB9HjHyvmE5JGhCmQB74ihxzud8zCDvHTJ9Xv |
| 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 | 6 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 | 3A96BH5EL5f5m4PNC52zWV… slot 468,476,966
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 09:35:25 UTC Slot 468,476,966, which is the chain's own clock for this moment. |
| Curve completed | 2026-11-12 09:41:05 UTC +5m 40s 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 | noskcaJ |
| Description | 100% fee to Jackson via BagsPay |
| Metadata held | sha256 817e701ef44959ca70c0b356f53dcc293b22d4dafd1521bd279c85d1ec50e280 · 338 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 0a516b5449fd4f1bbd50d016b2582107274fa61ec5fb7f4c624d82825d226228 · 24,810 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-12 09:35 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.