BRUME
Only 1 outside buyer bought its curveRead 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 1 outside buyer bought on the bonding curve before it graduated.
At launch
| Created | 2026-10-02 11:30 UTC |
| Creator | 2YWMzreBrvUCbzQ9t3fQRu1DJAC4n8ZQPLyWxRUbxJhy |
| Creator took | 0.4% of supply in the first block |
| Outside buyers | 1 distinct wallets, not counting the creator, bought on the bonding curve: 1 within the first 30s, 3 bundled into the creation block. |
| Graduated | 26 min after launch |
| Curve, read on chain | Not re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers. |
| Creator sold | not while we watched |
| Recorded from | Fgi7yG3pgP8BbfAN2Bgv8b… slot 452,597,166
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 11:30:32 UTC Slot 452,597,166, which is the chain's own clock for this moment. |
| Creation block | 3 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 1 distinct buyer, 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-10-02 11:57:01 UTC +26m 29s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 12:00:05 UTC +29m 33s
1.017e-6 SOL per token.
Reported by a third-party price feed with no trade witnessed, which is a materially weaker claim than a
decoded one.
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 | No other launch we hold a picture for used this one. |
| This ticker | On 6 launches from 5 creator wallets, including this one. See them → |
Pool
| Liquidity | 135.9 SOL |
| Read from chain | 2026-10-02 14:44 UTC, just now |
What this launch claimed to be
| Name | BRUME |
| Description | Technologies to hide yourself in plain sight |
| Metadata held | sha256 bce0fff14c510b6650d7156eb21246bfdb4ea37e5e180ff0d60c7ea65dd970bf · 304 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 643739c25d21da9ea3af7b201fbd1aa83dfc8d37c0edf8dcc7e1800897df5e67 · 35,385 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 11:30 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.