NexaPay
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 1.1 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 20:55 UTC |
| Creator | 8T8jJSxQhVNBWanv3khRtSC8VTcDpS1gdJRAN1kk7mRR |
| Creator took | 2.8% of supply in the first block |
| Outside buyers | 815 distinct wallets, not counting the creator, bought on the bonding curve: 106 within the first 30s, 11 bundled into the creation block. |
| Graduated | 5 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 | 61BHg4GRfMEXkn7eV3oVCd… slot 451,755,253
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 20:55:17 UTC Slot 451,755,253, which is the chain's own clock for this moment. |
| Creation block | 11 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 106 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-29 21:00:43 UTC +5m 26s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-29 21:00:43 UTC +5m 26s
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 ticker | On 3 launches from 3 creator wallets, including this one. See them → |
Pool
| Liquidity | 1.1 SOL |
| Read from chain | 2026-10-01 06:56 UTC, just now |
What this launch claimed to be
| Name | NexaPay |
| Metadata held | sha256 7576469485ac8fd74d415403054023c3f8c3bd28c784e15d5362713c6aac59fe · 243 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 20:56 UTC. |
| Picture | Not captured, so we cannot show what it published. That is our storage budget, not a finding about the launch. |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 20:55 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.