Its own first blocks
Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.
At launch
| Created | 2026-11-20 05:47 UTC |
| Creator | 6HQceUPAR8aUCpvg9dRF9RYgFNKc1PFLxbE14vkUWQ31 |
| Creator took | 3.4% of supply in the first block |
| Outside buyers | 7 distinct wallets, not counting the creator, bought on the bonding curve - the automatic market a launch starts on, which has to fill up before the token can trade anywhere else: 6 within the first 30s, 0 in the very same block the token was created in. |
| Graduated | 0 min after launch |
| Curve on chain | Complete. We read the bonding curve account 6.6 h ago and it was finished. Checked 2026-11-20 10:06 UTC. |
| Creator sold | not while we watched |
| Recorded from | 4F7b11ZWEXkNT2tfyd3gTS… slot 471,625,243
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-11-20 05:47:09 UTC Slot 471,625,243, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Curve completed | 2026-11-20 05:47:36 UTC +27s Confirmed against the venue's own completion state. |
| Thirty seconds in | 6 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. |
| Highest price seen | 2026-11-20 05:48:11 UTC +1m 02s
2.457e-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 | No other launch we hold a picture for used this one. |
Pool
We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.
What this launch claimed to be
| Name | BRUVIMEMES |
| Description | Official Coin of BRUVIMEMES |
| Metadata held | sha256 ec6125a4576e00b734fc01216a5a3809e39b71311403fb19ebe73ba710305947 · 261 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 7e16e263d3e0762cf334b37fc16e69e7bb91d7f7298fcbd8232d6063aac85098 · 32,796 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-20 05:47 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.