SFOMO
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.
findingIt left the curve 0s after launch.
noteOnly 1.8 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-01 18:15 UTC |
| Creator | 2fwc9jLAzDNmTDX1AbU5yMDmWn1Lt2ATYpLK3RnCt89M |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 10 distinct wallets, not counting the creator, bought on the bonding curve: 10 within the first 30s, 10 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 | 4mPo94AHjW9oBQjT8xYabH… slot 452,365,331
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 18:15:53 UTC Slot 452,365,331, which is the chain's own clock for this moment. |
| Creation block | 10 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-10-01 18:15:53 UTC +0s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-01 18:15:53 UTC +0s
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. |
| Thirty seconds in | 10 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. |
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 2 launches from 2 creator wallets, including this one. See them → |
Pool
| Liquidity | 1.8 SOL |
| Read from chain | 2026-10-02 03:20 UTC, just now |
What this launch claimed to be
| Name | SuperFomo |
| Description | he got a cape, saw one green candle and immediately decided he was the main character. now he’s flying around the chart, buying first and thinking about it later. pretty much just fomo with superpowers. |
| Metadata held | sha256 31d4bbebc51dc2ef7652623391c23c45e34c08d449e1db867b416e876682f675 · 518 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-01 18:15 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.