JaneHoe
The curve completed 38s 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 38s after launch.
noteOnly 1.7 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 03:13 UTC |
| Creator | 8nDgbNcP9EfmSEmj2PZiALi7hZ3wQNtPVCB3G32uD8xn |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 55 distinct wallets, not counting the creator, bought on the bonding curve: 0 within the first 30s, 0 bundled into the creation block. |
| Graduated | 1 min after launch |
| Curve, read on chain | Not re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers. |
| Creator sold | not while we watched |
| Recorded from | 2xoQHUka7XAr5RfNLT8zSq… slot 452,485,550
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:13:14 UTC Slot 452,485,550, 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 | No buyer, 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:13:52 UTC +38s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 03:13:52 UTC +38s
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 | On 4 launches from 4 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 20 launches from 15 creator wallets, including this one. See them → |
| This document | Byte-identical to 4 other launches' metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 4 other creator wallets, across 3 shared artifacts, each matched by hash. Together they sit in a linked group of 5 creator wallets. See the linked wallets → |
Pool
| Liquidity | 1.7 SOL |
| Read from chain | 2026-10-02 11:56 UTC, just now |
What this launch claimed to be
| Name | I am a liar |
| Metadata held | sha256 f16cbe164913d78d1ed39dc18ad2d066d28e8604b416d560fbf6627122fbb83c · 196 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 d415cac3246a3cf84a0cc1fc721e2f68c751c7667d8f5ac03b1f7db2791d497f · 336,953 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 03:13 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.