nomnom
The creator took 22% of supply at launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
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.
noteThe creator took 22.4% of supply at launch.
noteThe creator sold while we were watching.
noteOnly 5.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 03:36 UTC |
| Creator | DJ4aJcphMkgLNagjegWsFMjFKSSAFopCTBzEhghHuksH |
| Creator took | 22.4% of supply in the first block |
| Outside buyers | 568 distinct wallets, not counting the creator, bought on the bonding curve: 173 within the first 30s, 12 bundled into the creation block. |
| Graduated | 3 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 8.8 h ago and it was finished. Checked 2026-10-02 04:01 UTC. |
| Creator sold | yes |
| Recorded from | LhLgaFmfULKxtNZVZghDuG… slot 452,490,839
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 03:36:41 UTC Slot 452,490,839, which is the chain's own clock for this moment. |
| Creation block | 12 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 173 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-10-02 03:39:43 UTC +3m 02s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-10-02 03:39:43 UTC +3m 02s
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 4 launches from 3 creator wallets, including this one. See them → |
Pool
| Liquidity | 5.0 SOL |
| Read from chain | 2026-10-02 12:47 UTC, just now |
What this launch claimed to be
| Name | nomnom |
| Description | Lets do this! |
| Metadata held | sha256 5fcd8639769cc73be8f07fbbe9530201619f0115efe80421e265c92e4dcec947 · 312 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 dcbd24ac3423d630de99ec2786b36368268c36855fb233fc8a34bba4da3add9f · 18,692 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 03:36 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.