What this launch shares with other launches
Free on this page: that each of these exists, and how many. The list behind a count, meaning which launches, which wallets and the transaction for each, opens with a free account for five lists, or with Brand Protection at $79 a month for every list on every record. This one launch can also be kept as a $49 document with its identical-file and creator lists, further down this page.
Its own first blocks
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.
At launch
| Created | 2026-11-14 12:17 UTC |
| Creator | 5CH9iCRvRmX43p2snYVmbuBL2Nokk6XFvqBy1GF8q8iy |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 285 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: 46 within the first 30s, 5 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together. |
| 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 while we watched |
| Recorded from | 4EHcKKhLXBJFrWFVKRW8t4… slot 469,324,878
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | 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-14 12:17:50 UTC Slot 469,324,878, which is the chain's own clock for this moment. |
| Creation block | 5 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 46 distinct buyers, 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. |
| Curve completed | 2026-11-14 12:24:15 UTC +6m 24s 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.
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 | ni hao chud |
| Description | |
| Metadata held | sha256 0a3396413fd3747995df822bb73ba4b80541889ba046e8dd92695260199f656b · 316 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 6deebc24bd9b827ac039135c51d7c21dfe485dc6b301a3398540911b7d777c19 · 99,298 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-14 12:17 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.