BLOB
Checked, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record; none is present. Separately, the pool balance was below our threshold when it was last read - a present-tense measurement with its own age, stated below, and not part of the launch record.
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.
noteOnly 1.7 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 15:51 UTC |
| Creator | Fxq7x8py3XAcyDXeF66Cmc9o7LTsfLqDMCFeFNHy92EZ |
| Creator took | 3.4% of supply in the first block |
| Outside buyers | 666 distinct wallets, not counting the creator, bought on the bonding curve: 123 within the first 30s, 4 bundled into the creation block. |
| Graduated | 5 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 5.0 h ago and it was finished. Checked 2026-09-30 16:02 UTC. |
| Creator sold | not while we watched |
| Recorded from | 2ANV9xZ1LY1JabQzK8n7sU… slot 452,010,107
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 15:51:32 UTC Slot 452,010,107, which is the chain's own clock for this moment. |
| Creation block | 4 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 123 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 15:56:08 UTC +4m 36s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-09-30 15:56:13 UTC +4m 42s
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 9 launches from 9 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 52 launches from 46 creator wallets, including this one. See them → |
| This document | Byte-identical to 4 other launches' metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 8 other creator wallets, across 3 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.7 SOL |
| Read from chain | 2026-09-30 21:01 UTC, just now |
What this launch claimed to be
| Name | blob |
| Metadata held | sha256 70cac69bbc270d93b8cefc2b66f930e994bd2ee032556f76d6fa2344850ba843 · 245 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 ece4c5b734afd9b14fc43a19fa3c501d2b67e4ddbaddaa1ad12700351a591f3d · 10,666 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 15:51 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.