FAIRS
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 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 06:20 UTC |
| Creator | 2kPdK6ZEU9UH72s5mVUQTUv5y4sEkwX6YoYHS1jTwRfS |
| Creator took | 0.4% of supply in the first block |
| Outside buyers | 36 distinct wallets, not counting the creator, bought on the bonding curve: 6 within the first 30s, 0 bundled into the creation block. |
| Graduated | 37 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 | xVEP2ToA2UdhPdURH4r4hs… slot 451,881,911
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:20:03 UTC Slot 451,881,911, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| 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-09-30 06:22:58 UTC +2m 55s
5.198e-8 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. |
| Curve completed | 2026-09-30 06:56:35 UTC +36m 32s 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 2 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 9 launches from 8 creator wallets, including this one. See them → |
| This creator | 8 earlier launches, 0 confirmed graduated on chain. See the creator's launches → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-10-01 23:51 UTC, just now |
What this launch claimed to be
| Name | LAFAIRS |
| Metadata held | sha256 0dd08271d95d81f75f67633b911854d5ddcb3f4fecd4a7e5589ded82e48c8c94 · 294 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:21 UTC. |
| Picture held | sha256 1377239a183167e598f3c2375ebfd876d1f60ba1a22be50493ae2dc0ad7b8182 · 213,544 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 06:20 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.