CANDACE
Checked, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record; 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.
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.
noteOnly 34.7 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-28 20:23 UTC |
| Creator | 8KZwhx9iBizJjW96PG8KpTbRrvGqiLnNrCUQ8KvsvQ51 |
| Creator took | 9.7% of supply in the first block |
| Outside buyers | 1,164 distinct wallets, not counting the creator, bought on the bonding curve: 26 within the first 30s, 5 bundled into the creation block. |
| Graduated | 3.3 h 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 | 3GXUzdkmPXbeQbcqSspmdR… slot 451,425,329
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-28 20:23:30 UTC Slot 451,425,329, which is the chain's own clock for this moment. |
| Creation block | 5 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 26 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-09-28 23:42:47 UTC +3h 19m 17s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-28 23:42:47 UTC +3h 19m 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 9 launches from 8 creator wallets, including this one. See them → |
Pool
| Liquidity | 34.7 SOL |
| Read from chain | 2026-09-29 05:18 UTC, just now |
What this launch claimed to be
| Name | Letmelickyou13 |
| Metadata held | sha256 ee43a8539c8baac58541d61776fc0e98b11bc0bdd34f7df1675c6746724b8f6b · 408 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 5d12a69569009f1ea58cbeb86d50a17ed4240356fc6c656585b6fec0c45f5bc4 · 262,326 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-28 20:23 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.