🚀
The curve completed 22s 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 22s after launch.
noteThe creator sold while we were watching.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 15:15 UTC |
| Creator | 7FVfSdnR9VPGjMtmBP1Hz9C2DFTpoNX8gVVRmnimnGt9 |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 32 distinct wallets, not counting the creator, bought on the bonding curve: 4 within the first 30s, 0 bundled into the creation block. |
| Graduated | 0 min 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 | yes |
| Recorded from | DLMcjeX1KM98XAHBZ5WVZu… slot 451,679,393
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 15:15:58 UTC Slot 451,679,393, 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 15:16:19 UTC +22s Confirmed: a PumpSwap pool was found for it. |
| Thirty seconds in | 4 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. |
| Highest price seen | 2026-09-29 15:16:28 UTC +31s
2.086e-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 99 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 226 launches from 58 creator wallets, including this one. See them → |
| This document | Byte-identical to 56 other launches' metadata document. See them → |
| This creator | 3,153 earlier launches, 44 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 7 other creator wallets, across 13 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-09-30 21:44 UTC, just now |
What this launch claimed to be
| Name | 🚀 |
| Description | to the moon |
| Metadata held | sha256 0dec636ce6890dc894ede5bb88e5c06ef7a127fc9d3fc12053b4813c894194bc · 197 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 15:16 UTC. |
| Picture held | sha256 6207d0fe615ee772a3360b3d665e0b07347d89067399b84e244f95d1c8f4ca8b · 72,859 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 15:15 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.