Yaniv
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 6.3 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 09:05 UTC |
| Creator | 3YkRetphMNxPe7p4L4EioK2Aiqqwxw2WvUWQS8NffNRY |
| Creator took | 3.4% of supply in the first block |
| Outside buyers | 887 distinct wallets, not counting the creator, bought on the bonding curve: 32 within the first 30s, 2 bundled into the creation block. |
| Graduated | 15 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 1.3 days ago and it was finished. Checked 2026-09-30 09:32 UTC. |
| Creator sold | not while we watched |
| Recorded from | 2bGsno74jjjin2wRwGNUoe… slot 451,919,075
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 09:05:31 UTC Slot 451,919,075, 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 | 32 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 09:20:31 UTC +15m 00s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-09-30 09:20:31 UTC +15m 00s
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 32 launches from 32 creator wallets, including this one. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 2 shared artifacts, each matched by hash. Together they sit in a linked group of 2 creator wallets. See the linked wallets → |
Pool
| Liquidity | 6.3 SOL |
| Read from chain | 2026-10-01 17:44 UTC, just now |
What this launch claimed to be
| Name | The Plane Hero |
| Description | STAY |
| Metadata held | sha256 d9419088356b569e627ea1fc660c4b0187027311520d5ab9c2828ef720f468f2 · 302 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-10-01 09:05 UTC. |
| Picture held | sha256 d10d06b9a4e8d27e2f08b5f2f2403d0a703f305689da4ba7245b5fbb676b7be6 · 27,670 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 09:05 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.