4.6%of supply taken by the creator in the first block
597outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
217launches carry this ticker, from 186 creator wallets11other launches declared this same launch document, byte for byte
12other launches used this exact picture file
No finding either wayWe watched this launch and ran the launch-record tests on it: what the creator took in the first block, how many wallets bought on the curve, how fast the curve filled, and whether a single buy completed it. None of them fired, and a marker is one of those tests firing. We still do not head this record 'no markers found': that line is kept for launches whose curve we watched fill slowly with at least thirty outside buyers, and this one did not complete a curve at all. Those tests read this launch's own first blocks only. What it shares with other launches is counted below and is not part of this answer. Neither endorsed nor accused.
Also recorded, and not part of the finding above: this picture is on 12 other launches from 10 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.
noteThe creator sold while we were watching.
noteOnly 2.2 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-11-10 22:51 UTC |
| Creator | GtKDKY9CDkbcuzUctLvBmx689iF8mQwubKULeW6CrAEf |
| Creator took | 4.6% of supply in the first block |
| Outside buyers | 597 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: 124 within the first 30s, 10 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together. |
| Graduated | 3 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 | yes |
| Recorded from | 4a1jbs7tmhksq4CSnMX5ML… slot 467,895,083
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-11-10 22:51:31 UTC Slot 467,895,083, which is the chain's own clock for this moment. |
| Creation block | 10 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 124 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. |
| Curve completed | 2026-11-10 22:54:42 UTC +3m 12s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-11-10 22:54:42 UTC +3m 12s
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 13 launches from 10 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 217 launches from 186 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 11 other launches, across 9 creator wallets in all. Across the archive, 33% of the launches whose document we hold carry one byte-identical to a different creator's. See them → |
| Files shared with other wallets | Launches by this creator were made with files byte-identical to those of 8 other creator wallets, across 2 shared files, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. Across the archive, 63.9% of launches come from a creator linked to at least one other wallet this way. See the linked wallets → |
Pool
| Liquidity | 2.2 SOL |
| Read from chain | 2026-11-11 16:34 UTC, just now |
What this launch claimed to be
| Name | Chop |
| Metadata held | sha256 8bb1d986c8bc40a6cea12afd8df996f32d0753efda83cd00d2022befebc1403a · 287 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 c0ecfbc98b2dddad4ff0ed828422bc9c6e91e90d7e0eab4afc4af88d8011a986 · 144,727 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-10 22:51 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.