BALL
The curve completed 22s 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 22s after launch.
noteThe creator sold while we were watching.
noteOnly 8.6 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 19:01 UTC |
| Creator | EWdQrNdWthBSBDafiTujSm1W4h3r8DL5uqTsezDQeSCQ |
| Creator took | 0.4% of supply in the first block |
| Outside buyers | 315 distinct wallets, not counting the creator, bought on the bonding curve: 315 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 | yes |
| Recorded from | 3J4XDcq7pUrpFDZbC1uGvs… slot 451,729,701
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-29 19:01:04 UTC Slot 451,729,701, 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-29 19:01:26 UTC +22s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-29 19:01:32 UTC +29s
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 | 315 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 | No other launch we hold a picture for used this one. |
| This ticker | On 222 launches from 79 creator wallets, including this one. See them → |
| This creator | 1 earlier launch, 0 confirmed graduated on chain. See the creator's launches → |
Pool
| Liquidity | 8.6 SOL |
| Read from chain | 2026-10-01 05:39 UTC, just now |
What this launch claimed to be
| Name | Balliquidity |
| Metadata held | sha256 8252d3839fa735d3cd34e54e6b0deb627c7bf72a63b4adfded940ff392a81ec8 · 300 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. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-09-30 19:02 UTC. |
| Picture held | sha256 973d85daff8e04d7fc6a00a2ffdbc7ab2a947359a171c5dd04b8364017e33159 · 7,894 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 19:01 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.