CLONE
The curve completed 13s after launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
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.
findingIt left the curve 13s after launch.
noteOnly 0.9 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-20 04:35 UTC |
| Creator | FpLSB523rcYCY7CVYjU2Jp76S1Bkj65FFfWCQxx37bf5 |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 17 distinct wallets, not counting the creator, bought on the bonding curve: 17 within the first 30s, 0 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Not read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch. |
| Creator sold | not while we watched |
| Recorded from | 2hTU6856Wz4JVfFvV5Sq8K… slot 448,624,940
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-20 04:35:17 UTC Slot 448,624,940, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Curve completed | 2026-09-20 04:35:30 UTC +13s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-20 04:35:30 UTC +13s
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. |
| Thirty seconds in | 17 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. |
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 5 launches from 4 creator wallets, including this one. See them → |
| This creator | 41 earlier launches, 3 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 33 other creator wallets, across 53 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 | 0.9 SOL |
| Read from chain | 2026-09-20 10:24 UTC, just now |
What this launch claimed to be
| Name | Clone Carson |
| Metadata held | sha256 8d43d9136738ad64a7f5da12ae5901a23c2492e138772dfd8b3dd76bde6c6a93 · 320 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 b0c11d551e9e2756a181b472f3d039a93b905bac2f38189610d1e1a470253b3a · 35,714 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-20 04:35 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.