3,524,935 launches on record
Coverage from 2 Sep 2026
Archive read 13:18 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 03:23 UTC

TST2

Test Two

229K8XjArevCYSiqg9L5nigTwhXcs1BzgXht7FD3fhDZ Solscan
0.0%of supply taken by the creator in the first block
Yesreached a graduation threshold while we watched
22launches carry this ticker, from 21 creator wallets
1other launch used this exact picture file
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 1 other launch from 2 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, 56.3% 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 03:23 UTC
CreatormiZNowa79oWuEoc7G9ire4DqDomH1FjCoehX9pby8Tu
Creator took0.0% 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 1.7 days ago and it no longer existed, so the reading settles nothing either way. Read 2026-11-10 23:59 UTC.
Creator soldnot recorded - this venue's trades do not name the wallet
Recorded from4Uaz746pK2aSHyRp1XpAth… slot 467,567,787
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.
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 03:23:30 UTC
Slot 467,567,787, which is the chain's own clock for this moment.
Highest price seen2026-11-10 03:23:37 UTC +6s
2.330e-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.
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 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.3% of the launches whose picture we hold carry one a different creator also used. See them →
This tickerOn 22 launches from 21 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.5% wear one that more than one creator wallet has launched. See this ticker's page →

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
NameTest Two
Metadata heldsha256 07aa2a311d444cf20542e6d94c5533e70b7595ec0ba4a732eef073d815ab5262 · 566 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 7ed102061122e161138199100ef622d3e5824d362fba44ac0216652888b08ec6 · 66,883 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-11-10 03:23 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