blob
The curve completed 5s 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 5s after launch.
noteOnly 6.7 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-01 20:53 UTC |
| Creator | BLoBkEbwwBJ6tJJDEuBNujd9ZCx65FXdQZY2MEHeuJum |
| Creator took | 3.5% of supply in the first block |
| Outside buyers | 61 distinct wallets, not counting the creator, bought on the bonding curve: 61 within the first 30s, 8 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 | 3UxeiyfJmrdKVsP5SHmne4… slot 452,400,657
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 20:53:53 UTC Slot 452,400,657, which is the chain's own clock for this moment. |
| Creation block | 8 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-10-01 20:53:59 UTC +5s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-01 20:53:59 UTC +5s
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 | 61 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 55 launches from 51 creator wallets, including this one. See them → |
Pool
| Liquidity | 6.7 SOL |
| Read from chain | 2026-10-01 23:18 UTC, just now |
What this launch claimed to be
| Name | agent blob |
| Description | all shapes relax eventually |
| Metadata held | sha256 5c075ae4ff334407f6cc441f96687e3eae5987ee592eb3770a4ceba6e24f1764 · 283 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 20:53 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.