GMET
Nobody bought its curveRead 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 completed its bonding curve with zero outside buyers on record.
noteOnly 1.7 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-24 00:32 UTC |
| Creator | FWHifNz5hRsDqm8jhZ2GQ1eqetiUKN9c1Jte2czdVykt |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 0 distinct wallets, not counting the creator, bought on the bonding curve: 0 within the first 30s, 8 bundled into the creation block. |
| Graduated | 7 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 | 5v7oHQ6NQ4otcbzpnc7N6i… slot 449,866,737
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-24 00:32:06 UTC Slot 449,866,737, which is the chain's own clock for this moment. |
| Creation block | 8 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | No buyer, 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-24 00:38:52 UTC +6m 46s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-24 00:38:52 UTC +6m 46s
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 5 launches from 4 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 3 launches from 2 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| This creator | 28 earlier launches, 1 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 27 other creator wallets, across 33 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-25 05:20 UTC, just now |
What this launch claimed to be
| Name | gmet |
| Metadata held | sha256 071d855140070890aef54f6be95eeadfa645c342a5aba79a27a80a86dd085d79 · 340 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-25 00:33 UTC. |
| Picture held | sha256 c978596524ec2ae99ec288cc3440d3a36da2d1204ca8ab14455b6febd2563a26 · 80,006 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-24 00:32 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.