YAMAL
The curve completed 16s after launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
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.
findingIt left the curve 16s after launch.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 15:15 UTC |
| Creator | GkeyAeb6kSa6vm2bNuNArEEMTBR2ATcSifD1LMj9vQEL |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 34 distinct wallets, not counting the creator, bought on the bonding curve: 3 within the first 30s, 1 bundled into the creation block. |
| Graduated | 0 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 | 3XY9ywGAqKQG1xq6ZcTeCr… slot 451,679,241
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-29 15:15:17 UTC Slot 451,679,241, which is the chain's own clock for this moment. |
| Creation block | 1 wallet bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-29 15:15:33 UTC +16s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-29 15:15:36 UTC +20s
2.213e-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. |
| Thirty seconds in | 3 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. |
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 6 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 16 launches from 11 creator wallets, including this one. See them → |
| This document | Byte-identical to 3 other launches' metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 2 other creator wallets, across 3 shared artifacts, each matched by hash. Together they sit in a linked group of 3 creator wallets. See the linked wallets → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-09-30 23:21 UTC, just now |
What this launch claimed to be
| Name | YAMAL TOKEN |
| Description | Official Lamine Yamal fun base coin . Coins will be used in real world for merchandising and more. info and web site soon . |
| Metadata held | sha256 a6f5a0242907e6bc957a975adaf50021543d14153f08d0edd89c20601c1c09ea · 319 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-30 15:16 UTC. |
| Picture held | sha256 9ceaab65a9faea22398869368b2399e87719f71faab0168ab555f8f6d8b2a285 · 230,030 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 15:15 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.