3,991,504 launches on record
Coverage from 2 Sep 2026
Archive read 17:52 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection
The picture this launch published at birth

Launch record · observed at creation 2026-11-10 15:37 UTC

PAYBACK

PayBack

zjr1qqb3ASbPD2rK6K9aC29uCpgLvq2npJ9L9ATuzN9 Solscan

What this launch shares with other launches

Free on this page: that each of these exists, and how many. The list behind a count, meaning which launches, which wallets and the transaction for each, opens with a free account for 5 lists, or with Brand Protection at $79 a month for every list on every record. Watch this creator wallet: a free account is emailed the next time it launches. This one launch can also be kept as a $49 document with its identical-file and creator lists, further down this page.

Its own first blocks

1.2%of supply taken by the creator in the first block
Yesreached a graduation threshold while we watched
No finding either wayWe watched this launch and ran the launch-record tests on it: what the creator took in the first block, how many wallets bought on the curve, how fast the curve filled, and whether a single buy completed it. None of them fired, and a marker is one of those tests firing. We still do not head this record 'no markers found': that line is kept for launches whose curve we watched fill slowly with at least thirty outside buyers, and this one did not complete a curve at all. Those tests read this launch's own first blocks only. What it shares with other launches is counted below and is not part of this answer. Neither endorsed nor accused.

Also recorded, and not part of the finding above: this picture is on 3 other launches from 4 creator wallets in all. The finding reads this launch's own first blocks; these are about what it has in common with other launches. Both are counts, not findings. Across the archive, 57% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.

Each line below is one entry on this record. A finding is something we recorded that counts against the launch, a note is a weaker one, and not established means we could not settle the question either way - an absence, not a lesser warning.

not establishedThis launch was recorded live, but its venue's trade events do not name the wallet that traded. Who bought on the bonding curve, and whether the creator sold, are therefore not on our record - not zero, and not checked and cleared. The creator's share of supply, the launch's own claim about itself, and whether the curve completed are recorded as normal.

At launch

Created2026-11-10 15:37 UTC
Creator7bskmqky1hVNnka6qHHEuvEALL3AaWPUstvwtrGBYGHf
Creator took1.2% of supply in the first block
Outside buyersunknown distinct wallets, not counting the creator, bought on the bonding curve - the automatic market a launch starts on, which has to fill up before the token can trade anywhere else.
Graduatedyes; we did not record when
Curve on chainRead, and the account had gone. We went to the bonding curve account 10.4 days ago and it no longer existed, so the reading settles nothing either way. Read 2026-11-11 13:30 UTC.
Creator soldnot recorded - this venue's trades do not name the wallet
Recorded from5YXedZtq8y3bNMmHta9veZ… slot 467,773,419
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedcurve_buyers, unique_buyers, snap30_buyers, bundled_buyers - this launch's venue publishes trade events that do not name the wallet that traded, so no count of people can be taken from them - which is not zero and not a clean result. peak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against one; it is the record declining to state something. The column names link to their full entries in the published schema, which is where the rest of the reason is written down.

Order of events

Created2026-11-10 15:37:02 UTC
Slot 467,773,419, which is the chain's own clock for this moment.
Curve completedRecorded as complete; we did not record when.
Not confirmed. An inference from decoded trade volume that nobody ever confirmed, and where the curve account has since been read, the great majority of those returned incomplete.

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 pictureOn 4 launches from 4 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 57% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 110 launches from 101 creator wallets, including this one. Counted over the launches we watched at birth, the same basis as this ticker's own page, so the two cannot disagree. Across the launches we watched at birth that stated a ticker, 89.9% wear one that more than one creator wallet has launched. See this ticker's page →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 2 other creator wallets, across 2 shared files, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group of 3 creator wallets in all. Across the archive, 63.3% of launches come from a creator linked to at least one other wallet this way. See the linked wallets →

Pool

We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.

What this launch claimed to be

The picture this launch published at birth
NamePayBack
DescriptionIf the dev sells, you get paid. Every coin has a pot. Dev dumps, holders get it. Dev holds, dev gets it.
Metadata heldsha256 177d3a9c21e38b76695f79a4b414f7de49e2ebb2649d4ff14c26384ba87e85a6 · 368 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 heldsha256 73de104765ad4d600b0fcf55a2e16848f2f6c7060d1bc51f352e7c6075bb71e4 · 13,577 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-11-10 15:37 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.

Check another