JEV
The creator took 26% 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 26.4% of supply at launch.
At launch
| Created | 2026-09-19 22:00 UTC |
| Creator | FLEX1W2b7FxmP5Bpn47jpNG5prBcYdDbR2ATaMysGR2V |
| Creator took | 26.4% of supply in the first block |
| Outside buyers | 71 distinct wallets, not counting the creator, bought on the bonding curve: 4 within the first 30s, 0 bundled into the creation block. |
| Graduated | 3 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 | not while we watched |
| Recorded from | 5rghxzdTYvtxP51m4RunpY… slot 448,536,177
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-19 22:00:31 UTC Slot 448,536,177, 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 | 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-19 22:03:00 UTC +2m 29s
3.928e-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. |
| Curve completed | 2026-09-19 22:03:02 UTC +2m 31s Confirmed: a PumpSwap pool was found for it. |
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 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 153 launches from 119 creator wallets, including this one. See them → |
| This document | Byte-identical to 2 other launches' metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 2 other creator wallets, across 3 shared artifacts, each matched by hash. Together they sit in a linked group of 3 creator wallets. See the linked wallets → |
Pool
| Liquidity | 175.3 SOL |
| Read from chain | 2026-09-20 08:20 UTC, just now |
What this launch claimed to be
| Name | Black Box |
| Metadata held | sha256 6a216153c07c7e60c9a31b97271fe541a32b4d1fa26d156b170f73403f776bb7 · 190 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 62cfb80bfaf4e5b3b13b3accbeb234de09ba278f11c7588c075a91607e50c3a7 · 13,961 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-19 22:00 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.