NUH
Checked, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record; none is present. Separately, the pool balance was below our threshold when it was last read - a present-tense measurement with its own age, stated below, and not part of the launch record.
A record of what this launch was at birth, read from the Solana chain. The transaction it was decoded from is cited below: every figure here can be checked against the chain without trusting us. Not a prediction and not advice.
noteOnly 32.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-20 17:01 UTC |
| Creator | EmxN56hqR7f4xMht1qE5f4dNcfSWAZCJF3A8iNeF2dtN |
| Creator took | 17.7% of supply in the first block |
| Outside buyers | 368 distinct wallets, not counting the creator, bought on the bonding curve: 38 within the first 30s, 0 bundled into the creation block. |
| Graduated | 1.7 h after launch |
| Curve, read 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 | 4yMuRSd1pkyc5LkQrmT2U8… slot 448,793,119
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-20 17:01:47 UTC Slot 448,793,119, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Thirty seconds in | 38 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-09-20 18:41:36 UTC +1h 39m 50s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-20 18:41:36 UTC +1h 39m 50s
4.109e-7 SOL per token.
Decoded from an on-chain transaction that executed at that price.
A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not
here. |
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 picture | No other launch we hold a picture for used this one. |
| This ticker | On 40 launches from 6 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
Pool
| Liquidity | 32.0 SOL |
| Read from chain | 2026-09-22 02:54 UTC, just now |
What this launch claimed to be
| Name | I'm a demon with this nuh |
| Metadata held | sha256 2944473cf5b96b6e0ee160c19194c19a8694d04c82f69c96f39755f1a1669123 · 1,006 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. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-09-21 17:15 UTC. |
| Picture held | sha256 8312ef2b991472e4b7445a432a0ab87192d68ba511bd538a28e877b8d2ba2e02 · 25,881 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-20 17:01 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.