Also recorded, and not part of the finding above: this picture is on 33 other launches from 30 creator wallets in all. The finding reads this launch's own first blocks; these are about what it has in common with other launches. Both are counts, not findings. Across the archive, 56.2% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.
Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.
At launch
| Created | 2026-11-11 21:10 UTC |
| Creator | GXJezwSVpDGs3PxPjCFWqRQF6dGsZmuN6VtfvQSA6VxS |
| Creator took | 15.3% of supply in the first block |
| Outside buyers | 300 distinct wallets, not counting the creator, bought on the bonding curve - the automatic market a launch starts on, which has to fill up before the token can trade anywhere else: 1 within the first 30s, 0 in the very same block the token was created in. |
| Graduated | 26 min after launch |
| Curve 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 | 539HrdpPp3tFeXr8EnjpMP… slot 468,269,266
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-11-11 21:10:59 UTC Slot 468,269,266, 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 | 1 distinct 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-11-11 21:36:47 UTC +25m 47s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-11-11 21:36:47 UTC +25m 47s
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 34 launches from 30 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.2% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 174 launches from 140 creator wallets, including this one. Counted over the launches we watched at birth, the same basis as this ticker's own page, so the two cannot disagree. Across the launches we watched at birth that stated a ticker, 89.5% wear one that more than one creator wallet has launched. See this ticker's page → |
| This document | The same launch document, byte for byte, as 1 other launch, all of them this same creator's. Across the archive, 12% of the launches whose document we hold carry one only their own creator reused. See them → |
Pool
| Liquidity | 13.4 SOL |
| Read from chain | 2026-11-12 05:19 UTC, just now |
What this launch claimed to be
| Name | sexsen mesk |
| Description | Deployed using https://j7tracker.io |
| Metadata held | sha256 cf386a30a4358cba0480b294c5a3c1fd9e88c155dd61d0de919be84655b8c196 · 291 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 f73a21fb27c67769c48a9bfa570462e1732564a2c6577bad44e0c1be58fbfe09 · 11,876 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-11 21:10 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.