token
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.
At launch
| Created | 2026-10-01 15:36 UTC |
| Creator | Charmy1UtDkndXuv9SaTE2i9WGm2wDwZKyhD7jmo9nsT |
| Creator took | 9.6% of supply in the first block |
| Outside buyers | 568 distinct wallets, not counting the creator, bought on the bonding curve: 166 within the first 30s, 3 bundled into the creation block. |
| Graduated | 2 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 | yes |
| Recorded from | bjp4AhaKYQxZe6wCuDjmyS… slot 452,329,650
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 15:36:03 UTC Slot 452,329,650, which is the chain's own clock for this moment. |
| Creation block | 3 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 166 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 15:38:05 UTC +2m 02s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-01 15:38:05 UTC +2m 02s
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 58 launches from 41 creator wallets, including this one. See them → |
| This creator | 646 earlier launches, 79 confirmed graduated on chain, 68 with findings on record. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 307 other creator wallets, across 460 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 | 43.2 SOL |
| Read from chain | 2026-10-01 23:07 UTC, just now |
What this launch claimed to be
| Name | token |
| Metadata held | sha256 74cc6509a44b53651a827f5b34e9d389b919a2f67e114584727f8d08162f0b3e · 286 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 d4170f602af41df87e5d5fab7608770757c2ed637537a8c70fd96f5d26962122 · 5,663 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 15:36 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.