BEEaTLES
The curve completed 34s 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 34s after launch.
noteThe creator sold while we were watching.
noteOnly 0.2 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 23:43 UTC |
| Creator | 5hXcPHqFrFnFJNAuLARn9XcfZPYeJieQ3PjpwUoZAmhW |
| Creator took | 1.4% of supply in the first block |
| Outside buyers | 24 distinct wallets, not counting the creator, bought on the bonding curve: 2 within the first 30s, 0 bundled into the creation block. |
| Graduated | 1 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 | 4gPpR3c1fmra5k4D4HkuCR… slot 452,115,880
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-30 23:43:49 UTC Slot 452,115,880, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Thirty seconds in | 2 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. |
| Curve completed | 2026-09-30 23:44:23 UTC +34s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-30 23:46:30 UTC +2m 41s
4.781e-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. |
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.
Pool
| Liquidity | 0.2 SOL |
| Read from chain | 2026-10-01 03:12 UTC, just now |
What this launch claimed to be
| Name | black BEEaTLES |
| Description | NO UTILITY. JUST PURE MEME ENERGY. |
| Metadata held | sha256 e4da062b5de7ced106f21902b5b5eca420435f0a3013c859427a5ff4ae13f0ba · 340 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-09-30 23:43 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.