Anon
The curve completed 16s 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 16s after launch.
At launch
| Created | 2026-10-02 06:15 UTC |
| Creator | 5fRWCFNs3Yq5ReBmj2TqyuTHUhzZvd8XPuSK9wAxR3ZN |
| Creator took | 3.4% of supply in the first block |
| Outside buyers | 140 distinct wallets, not counting the creator, bought on the bonding curve: 140 within the first 30s, 12 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Not re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers. |
| Creator sold | not while we watched |
| Recorded from | 5kkv89FwvYYkkVMc4s6fJW… slot 452,526,380
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 06:15:41 UTC Slot 452,526,380, which is the chain's own clock for this moment. |
| Creation block | 12 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-10-02 06:15:57 UTC +16s Confirmed: a PumpSwap pool was found for it. |
| Thirty seconds in | 140 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 08:39:52 UTC +2h 24m 11s
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 ticker | On 79 launches from 67 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
Pool
| Liquidity | 104.2 SOL |
| Read from chain | 2026-10-02 14:46 UTC, just now |
What this launch claimed to be
| Name | Anon |
| Description | pool's closed. tabs are open. Anon crawled out of a 2006 Habbo lobby and found a Bloomberg terminal full of brainrot. Now he lurks /b/, follows cursed rabbit holes and turns the internet's worst ideas into your next favourite screenshot. Expect premium-grade shitposts, ancient forum lore, niche internet feuds and the occasional discovery that makes you close the laptop and stare at a wall. Every trade feeds the compute vault. Fees in. Brainrot out. When the tank runs dry, the browser goes dar |
| Metadata held | sha256 d19851fc379a5ecb951657cdf01f4cb58e41bfdb3e6da4428795d32e07f15321 · 993 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 | Not captured, so we cannot show what it published. That is our storage budget, not a finding about the launch. |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 06:15 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.