ZPAY
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 4.9 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-20 19:32 UTC |
| Creator | 3HkKdjCXo47oCLAiEAGRtQmbwQFZhxGNKsEufwpJinU4 |
| Creator took | 3.0% of supply in the first block |
| Outside buyers | 788 distinct wallets, not counting the creator, bought on the bonding curve: 246 within the first 30s, 5 bundled into the creation block. |
| Graduated | 4 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 | 4Dge4z1r6SDgfz53EezBzK… slot 448,826,836
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-20 19:32:08 UTC Slot 448,826,836, which is the chain's own clock for this moment. |
| Creation block | 5 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 246 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-20 19:36:27 UTC +4m 19s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-20 19:36:27 UTC +4m 19s
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 2 launches from 2 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 7 creator wallets, including this one. See them → |
| This document | Byte-identical to 2 other launches' metadata document. See them → |
| This creator | 2 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 2 other creator wallets, across 5 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 | 4.9 SOL |
| Read from chain | 2026-09-22 02:52 UTC, just now |
What this launch claimed to be
| Name | ZPAY |
| Metadata held | sha256 558734e4d8a3fd82e730e8234c07fc2f2fa37185bd4dfe6ba08f324b6d80dc84 · 290 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 9e9256de320dbd26a1e46b35a83080793f73e70ea44b777838b9a968b82820f2 · 567,730 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-20 19:32 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.