woin
The curve completed 51s 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 51s after launch.
noteOnly 3.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-28 22:30 UTC |
| Creator | Bh5cAbv9S9HnVHEYwEfgWhgwQYfzNgzFdksUPUchwC9p |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 76 distinct wallets, not counting the creator, bought on the bonding curve: 63 within the first 30s, 7 bundled into the creation block. |
| Graduated | 1 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 6.2 h ago and it was finished. Checked 2026-09-28 22:32 UTC. |
| Creator sold | not while we watched |
| Recorded from | 2AQs4vd36m15aPobUR8wFE… slot 451,453,670
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 22:30:01 UTC Slot 451,453,670, which is the chain's own clock for this moment. |
| Creation block | 7 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 63 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 22:30:52 UTC +51s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-09-28 22:30:52 UTC +51s
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 | No other launch we hold a picture for used this one. |
| This ticker | On 2 launches from 2 creator wallets, including this one. See them → |
Pool
| Liquidity | 3.0 SOL |
| Read from chain | 2026-09-29 04:45 UTC, just now |
What this launch claimed to be
| Name | wojak + coin = |
| Metadata held | sha256 7b10ac213fb4f37e0919c169d73f8d6922c8a376cc9263acd565486286e016ed · 311 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 9d4953afb70b32202c4972481d03cf9b09099d582ca14116ffaaffd46f357254 · 987,590 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-28 22:30 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.