4.1%of supply taken by the creator in the first block
550outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
12launches carry this ticker, from 10 creator wallets3other launches declared this same launch document, byte for byte
4other launches used this exact picture file
Checked at birth, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record - a marker being one of the launch-record tests below that fired - and none is present. Separately, the pool balance was below our threshold when it was last read - a present-tense measurement with its own age, stated below, and not part of the launch record.
Also recorded, and not part of the finding above: this picture is on 4 other launches from 5 creator wallets in all, and this creator has 2 other launches on record. 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.
noteOnly 35.6 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-11-09 19:38 UTC |
| Creator | 9Xt9Zj9HoAh13MpoB6hmY9UZz37L4Jabtyn8zE7AAsL |
| Creator took | 4.1% of supply in the first block |
| Outside buyers | 550 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: 56 within the first 30s, 4 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 | 29 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 | 2nvPbPvYVXLq8VfXNVPoan… slot 467,437,812
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-11-09 19:38:47 UTC Slot 467,437,812, which is the chain's own clock for this moment. |
| Creation block | 4 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 56 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-09 20:07:41 UTC +28m 54s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-11-09 20:08:38 UTC +29m 51s
5.191e-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 5 launches from 5 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 12 launches from 10 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 3 other launches, across 4 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 → |
| This creator | 2 earlier launches, 1 confirmed complete on chain, 1 with findings on record. Across the archive, 70.7% of launches come from a creator with more than one launch on record. See the creator's launches → |
| Files shared with other wallets | Launches by this creator were made with files byte-identical to those of 4 other creator wallets, across 3 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, 64% of launches come from a creator linked to at least one other wallet this way. See the linked wallets → |
Pool
| Liquidity | 35.6 SOL |
| Read from chain | 2026-11-11 19:18 UTC, just now |
What this launch claimed to be
| Name | CLMFND |
| Description | Claim your PumpFun fees. Even small amounts less than 0.02 SOL. |
| Metadata held | sha256 9fbd72a92fb07e239f07fe764de24ac942011977e480e95199e6505603a1c071 · 423 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-11-10 19:50 UTC. |
| Picture held | sha256 0ea4691e85b6d9cbf703b050d6a2116559ecba0b6b593c46fa891dc23c136a4f · 12,003 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-09 19:38 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.