Karen
No finding either wayWe watched this launch. It matches none of the patterns we record, and it does not meet every criterion for a record with no markers. Neither endorsed nor accused.
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 sold while we were watching.
noteOnly 4.2 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 16:37 UTC |
| Creator | 4HXb7ivgvjbHC3TBesmmD9LovH8tmTv9DZsq12GMvEpU |
| Creator took | 15.3% of supply in the first block |
| Outside buyers | 976 distinct wallets, not counting the creator, bought on the bonding curve: 221 within the first 30s, 9 bundled into the creation block. |
| Graduated | 5 min after launch |
| Curve, read 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 | 2TKsrgKtR9EqkqPMwRVgBe… slot 452,666,110
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 16:37:09 UTC Slot 452,666,110, which is the chain's own clock for this moment. |
| Creation block | 9 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 221 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-10-02 16:42:26 UTC +5m 17s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 16:42:26 UTC +5m 17s
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 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 84 launches from 41 creator wallets, including this one. See them → |
| This creator | 245 earlier launches, 7 confirmed graduated on chain, 1 with findings on record. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 159 other creator wallets, across 179 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 | 4.2 SOL |
| Read from chain | 2026-10-02 21:25 UTC, just now |
What this launch claimed to be
| Name | Karen |
| Metadata held | sha256 b626d5f4bf1bfcce139c34896ac4fb428fb2922acc383e8a20076e9d80315783 · 387 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 dd753a7cf48ec6a64803718994ff508e1eef69daf13cff4afdea4a8afc97cd6e · 14,840 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 16:37 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.