CLIPPY
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 1.7 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-01 21:23 UTC |
| Creator | 8Lohj9mbbM4zdDFQuuGeYV3wUHUKHPV8n7v2HRf64g56 |
| Creator took | 1.8% of supply in the first block |
| Outside buyers | 209 distinct wallets, not counting the creator, bought on the bonding curve: 91 within the first 30s, 21 bundled into the creation block. |
| Graduated | 2 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 | k5FcqchhBSjeUGe3BYehWa… slot 452,407,302
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-01 21:23:53 UTC Slot 452,407,302, which is the chain's own clock for this moment. |
| Creation block | 21 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 91 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-01 21:25:27 UTC +1m 34s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-01 21:25:27 UTC +1m 34s
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 12 launches from 12 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 644 launches from 104 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 2 shared artifacts, each matched by hash. Together they sit in a linked group of 2 creator wallets. See the linked wallets → |
Pool
| Liquidity | 1.7 SOL |
| Read from chain | 2026-10-02 03:12 UTC, just now |
What this launch claimed to be
| Name | CLIPPY |
| Metadata held | sha256 21f8c3243b67f239aa6e33e67a2665a78b88e37ca54e98c35adfb7161eea9000 · 251 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 50c7f587eb121c6d4d16d3d937f312b25aba6300fdb160c3f434fd25ca002408 · 180,858 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 21:23 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.