FOMOLYGUY
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 5 outside buyers bought on the bonding curve before it graduated.
findingIt left the curve 0s after launch.
noteOnly 2.5 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-27 23:54 UTC |
| Creator | Bb2gZkdXfmhuRpn7D8DtcLd9jjF4UdYyfmynvs3QJCaf |
| Creator took | 0.4% of supply in the first block |
| Outside buyers | 5 distinct wallets, not counting the creator, bought on the bonding curve: 5 within the first 30s, 5 bundled into the creation block. |
| Graduated | 0 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 | 24L46D4UzpkDPbmd1jUVeR… slot 451,150,396
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-27 23:54:34 UTC Slot 451,150,396, which is the chain's own clock for this moment. |
| Creation block | 5 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-27 23:54:34 UTC +0s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-27 23:54:34 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 | 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. |
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 | On 4 launches from 4 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 4 launches from 4 creator wallets, including this one. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 3 other creator wallets, across 2 shared artifacts, each matched by hash. Together they sit in a linked group of 4 creator wallets. See the linked wallets → |
Pool
| Liquidity | 2.5 SOL |
| Read from chain | 2026-09-29 03:15 UTC, just now |
What this launch claimed to be
| Name | FOMOly guy |
| Description | Not your average family guy. |
| Metadata held | sha256 cf8e91847288b4b726e6514f12bda04ebb7a0a8613c8660d7d9288b45f69b6e2 · 364 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 da91c547feaecd2bf72d8026d87f3e0050a2d3dbc2c038af6b76091c467b072c · 70,608 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-27 23:54 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.