MINARA
No finding either wayWe watched this launch. It matches none of the patterns we record, and it does not meet every criterion for a record with no markers. Neither endorsed nor accused.
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 sold while we were watching.
noteOnly 1.6 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-28 17:11 UTC |
| Creator | FW46vLtJiLacs5b3nvBEAj4bHY5NmTfrHXRuBUbQghAk |
| Creator took | 3.4% of supply in the first block |
| Outside buyers | 191 distinct wallets, not counting the creator, bought on the bonding curve: 67 within the first 30s, 5 bundled into the creation block. |
| Graduated | 3 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 | 2nfJyPmyNiZXdrjjUZWA6h… slot 451,382,462
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-28 17:11:52 UTC Slot 451,382,462, 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. |
| Thirty seconds in | 67 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-28 17:15:09 UTC +3m 17s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-28 17:15:09 UTC +3m 17s
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 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 37 launches from 30 creator wallets, including this one. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 2 other creator wallets, across 2 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets → |
Pool
| Liquidity | 1.6 SOL |
| Read from chain | 2026-09-29 21:45 UTC, just now |
What this launch claimed to be
| Name | minara |
| Description | - Fees to @minara via UsePaid |
| Metadata held | sha256 1a137a448c6f7e368d17d0585210aa7b2a91488e0f3986e284f8740a4818e777 · 365 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-29 17:12 UTC. |
| Picture held | sha256 bd0db53f4cdf69dd1b5a8e4531a8bee83161557a0aee7914eaa5870b66bf2be4 · 469,215 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-28 17:11 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.