Launch record · observed at creation 2026-11-12 15:59 UTC
2PMOHC
131pmohCniahC
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 15:59 UTC |
| Creator | DEVGgPtpV2WjpNnkpsQ14LM3bwvELMozwbxrQ473mAzs |
| 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 | 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 | 5HbQe2r2N9JJdeJxGt7L2g… slot 468,584,124
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 15:59:29 UTC Slot 468,584,124, which is the chain's own clock for this moment. |
| Curve completed | 2026-11-12 16:00:22 UTC +53s 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 | 131pmohCniahC |
| Description | https://x.com/ChainChomp131 |
| Metadata held | sha256 6baa9562a8173ce4e237ed8e8cd98e939508c22a570cb7598f7211ba9a1b1026 · 307 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 8ba38dc210478917606d1149f348743c67edc6499c2f0378d22cf5ba4ef1e854 · 17,179 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-12 15:59 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.