wenwew
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.
noteOnly 0.3 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-01 12:58 UTC |
| Creator | 9ecRdqNCBxwReiY2pxtnLeayeBzE1CrSSmKKJJGdmsaJ |
| Creator took | 5.0% of supply in the first block |
| Outside buyers | 21 distinct wallets, not counting the creator, bought on the bonding curve: 5 within the first 30s, 0 bundled into the creation block. |
| Graduated | 4 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 | bfEyjd3PcpKZygNo8fsdSs… slot 452,294,407
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 12:58:19 UTC Slot 452,294,407, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Thirty seconds in | 5 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. |
| Highest price seen | 2026-10-01 12:59:02 UTC +43s
1.077e-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. |
| Curve completed | 2026-10-01 13:02:42 UTC +4m 23s Confirmed: a PumpSwap pool was found for it. |
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 | No other launch we hold a picture for used this one. |
| This creator | 4 earlier launches, 1 confirmed graduated on chain. See the creator's launches → |
Pool
| Liquidity | 0.3 SOL |
| Read from chain | 2026-10-01 18:09 UTC, just now |
What this launch claimed to be
| Name | uinwwdoweeen |
| Metadata held | sha256 480ace4bc51bee1c5d15eea774643643740c9db15fd153cdd368455baa1cbcd2 · 223 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 60fa55351c5dfb58bb5f761a1cddc6c25d8e69e2ffb276c833f4ba0db68f3915 · 103,509 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 12:58 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.