www
The curve completed in the same batch of events as the 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.
findingOnly 4 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 0s after launch.
At launch
| Created | 2026-10-02 18:51 UTC |
| Creator | 642ujanZZzWLii3LJvg5NfLpnY12MkVeMeZrRGiStyyp |
| Creator took | 0.4% of supply in the first block |
| Outside buyers | 4 distinct wallets, not counting the creator, bought on the bonding curve: 4 within the first 30s, 4 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 7.1 h ago and it was finished. Checked 2026-10-02 19:01 UTC. |
| Creator sold | not while we watched |
| Recorded from | 4cAUcrZdktfUVCorppBvaS… slot 452,696,113
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 18:51:31 UTC Slot 452,696,113, which is the chain's own clock for this moment. |
| Creation block | 4 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-10-02 18:51:31 UTC +0s Confirmed against the venue's own completion state. |
| Thirty seconds in | 4 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-02 19:00:56 UTC +9m 25s
0.000e+0 SOL per token.
Source not recorded, which is every row written before 2026-09-10 - never that the peak was
unsourced.
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 | No other launch we hold a picture for used this one. |
| This ticker | On 265 launches from 214 creator wallets, including this one. See them → |
Pool
| Liquidity | 185.6 SOL |
| Read from chain | 2026-10-03 02:07 UTC, just now |
What this launch claimed to be
| Name | we will win |
| Description | same three letters. different sentence. we will win. $www |
| Metadata held | sha256 024734397df82212b0d2e63fbb3954f5902c5e41a4d8bb0d9bcb9dca66f65d2b · 326 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 3d524995db2aea6e87d79d73883a8c212e1af95012ac080b64150b7f08e37138 · 37,402 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 18:51 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.