NPC
The curve completed 19s after 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.
findingIt left the curve 19s after launch.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 21:23 UTC |
| Creator | Dym59nVb5HGXREHd11JcRytyP1Q2KmkmaxaUQX6KEGsv |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 24 distinct wallets, not counting the creator, bought on the bonding curve: 7 within the first 30s, 0 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 1.4 days ago and it was finished. Checked 2026-09-29 21:32 UTC. |
| Creator sold | not while we watched |
| Recorded from | 3QJcjbVa9gfwRsfrKhL3cp… slot 451,761,452
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-29 21:23:01 UTC Slot 451,761,452, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Curve completed | 2026-09-29 21:23:20 UTC +19s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-09-29 21:23:27 UTC +26s
1.408e-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. |
| Thirty seconds in | 7 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. |
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 | On 12 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 358 launches from 283 creator wallets, including this one. See them → |
| This document | Byte-identical to 10 other launches' metadata document. See them → |
| This creator | 21 earlier launches, 1 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 3 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-10-01 07:33 UTC, just now |
What this launch claimed to be
| Name | Non-Playable Coin |
| Metadata held | sha256 2b5cf1b335f35bb4b4e2b18cb4d2cc7b444c15f262dc3f0b11f513c0dc8d1742 · 198 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-30 21:24 UTC. |
| Picture held | sha256 9ac166002c4478ef90de2f6d53d5a86c05057b7300f50300e1e3abc6cc1ed1d3 · 27,340 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 21:23 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.