BPANDA
The creator took 26% of supply at 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.
noteThe creator took 26.5% of supply at launch.
noteThe creator sold while we were watching.
noteOnly 1.4 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-19 22:24 UTC |
| Creator | FWfiNJqnokt6SNfxEfBfd3JkZw8GPPMFZ3tL4GjtRoRV |
| Creator took | 26.5% of supply in the first block |
| Outside buyers | 270 distinct wallets, not counting the creator, bought on the bonding curve: 24 within the first 30s, 2 bundled into the creation block. |
| Graduated | 11 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 | 227z1EGSHvXsWAZ2mbvj7w… slot 448,541,643
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-19 22:24:57 UTC Slot 448,541,643, which is the chain's own clock for this moment. |
| Creation block | 2 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 24 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-19 22:35:46 UTC +10m 49s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-19 22:35:46 UTC +10m 49s
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. |
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 16 launches from 16 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 23 launches from 22 creator wallets, including this one. See them → |
Pool
| Liquidity | 1.4 SOL |
| Read from chain | 2026-09-20 05:28 UTC, just now |
What this launch claimed to be
| Name | Binance Panda |
| Description | All fees redirected to @binance via @UsePaid Fees to @binance via UsePaid |
| Metadata held | sha256 93663850b8cde21f56411940a7a91f94aff4289f26d82417530aed78a83e2ec8 · 321 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 fa271039223da9543be5b59a197ed2a2cd236b340dfe45911a06c2c58371853f · 77,770 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-19 22:24 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.