PUBG
The curve completed 40s 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 40s after launch.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-30 14:01 UTC |
| Creator | FjJuagkW5FzkDUg9CBtYjXesR32CodxWvQ9dD3sASDjD |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 27 distinct wallets, not counting the creator, bought on the bonding curve: 2 within the first 30s, 0 bundled into the creation block. |
| Graduated | 1 min after launch |
| Curve, read on chain | Incomplete. We read the bonding curve account 5.6 h ago and it had not finished, though a graduation event was recorded for it. This launch is not counted as a graduation anywhere on this site. Checked 2026-09-30 14:02 UTC. |
| Creator sold | not while we watched |
| Recorded from | 56Hruegn5e1rd1GGRBFvxX… slot 451,985,552
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 14:01:38 UTC Slot 451,985,552, 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 | 2 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 14:02:18 UTC +40s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-30 14:02:31 UTC +53s
1.678e-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 | No other launch we hold a picture for used this one. |
| This ticker | On 10 launches from 9 creator wallets, including this one. See them → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-09-30 19:40 UTC, just now |
What this launch claimed to be
| Name | PUBG MOBILE |
| Description | The coin was created to support PUBG Mobile streamers and quality content. |
| Metadata held | sha256 2ef84b7b6896479eb79770725599b5d9bfbe3f0792882eb39f6bbc3394e14426 · 304 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. |
| Picture held | sha256 a5501160a1e7332e1c9dd6bbfcc8244999c8f88df86e0ff7755068ef935328b4 · 14,651 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-30 14:01 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.