FZ1073
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 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 06:18 UTC |
| Creator | 673xcs51g3neU8oqAkkUHY5JLfmD16XYSWuZjNkY5VkM |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 251 distinct wallets, not counting the creator, bought on the bonding curve: 10 within the first 30s, 3 bundled into the creation block. |
| Graduated | 15 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 | not while we watched |
| Recorded from | 2ban6zUoa2xut5qiomA2za… slot 451,881,517
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 06:18:18 UTC Slot 451,881,517, 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. |
| Highest price seen | 2026-09-30 06:18:18 UTC
0.000e+0 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. |
| Thirty seconds in | 10 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 06:33:29 UTC +15m 11s Confirmed: a PumpSwap pool was found for it. |
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 34 launches from 22 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 87 launches from 66 creator wallets, including this one. See them → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-10-01 18:32 UTC, just now |
What this launch claimed to be
| Name | The Hijacked Plane |
| Metadata held | sha256 de6aa3f9e2b72d969bebb0514047805ac6fa70eefd52c4f635834f717f1becd0 · 359 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 06:19 UTC. |
| Picture held | sha256 6291a9ff8f182b4e97ea7d6f99f4118eedcb3be08fed2ddeffb4208d6ea37ae8 · 9,196 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 06:18 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.