1,752,162 launches on record
Coverage from 2 Sep 2026
Archive read 12:49 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

TRENDCOIN

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 creator has 798 other launches on record. 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. They are listed under Seen before, further down this page.

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.

87uoz7zYUMDT2qaCNFu4pabW69auTSVNQ7SM1TPDBNNd Solscan pump.fun

Cite this record as: Chain of Title, TRENDCOIN, mint 87uoz7zYUMDT2qaCNFu4pabW69auTSVNQ7SM1TPDBNNd, observed at creation 2026-09-25 04:37 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/87uoz7zYUMDT2qaCNFu4pabW69auTSVNQ7SM1TPDBNNd

At launch

Created2026-09-25 04:37 UTC
CreatorAN38on9YmoH6TQ7KEfnUY1mp88HdNG2m6iV9BgD5NTpK
Creator took0.0% of supply in the first block
Outside buyers7 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: 6 within the first 30s, 4 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together.
Graduatednot while we were watching
Curve on chainNothing to confirm. This launch never reached a graduation threshold while we watched, so there was no completion to check against the curve account. Most tokens end this way, and it is not a finding about them.
Creator soldnot while we watched
Recorded from2McDXxgBa2kPzJBgswqthn… slot 450,246,642
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Keep this launch as a document

A dated extract of this one launch, frozen at the moment you buy it: every other launch that carried the byte-identical picture or document, this creator's other launches, and what this register checked. A page you can send to someone, and a clean PDF from your browser's print dialogue.

No account needed; the link arrives by email and is permanent. It is this register's own output, with no signature and no attestation: the scoped, signed version written for a dispute is a provenance report. Everything on this page stays free.

Order of events

Created2026-09-25 04:37:07 UTC
Slot 450,246,642, which is the chain's own clock for this moment.
Creation block4 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in6 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.
Highest price seen2026-09-25 04:37:43 UTC +36s
2.890e-8 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 pictureNo other launch we hold a picture for used this one.
This tickerOn 21 launches from 19 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, 87% wear one that more than one creator wallet has launched. See this ticker's page →
This creator798 earlier launches, 1 confirmed complete on chain. Across the archive, 70.4% of launches come from a creator with more than one launch on record. See the creator's launches →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 32 other creator wallets, across 74 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 so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. Across the archive, 58.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
NameTRENDCOIN
Descriptionpure green candles
Metadata heldsha256 fed985d0273f96947c8d42ce7eef950162624088c9c0f5dd92e873b0939e4b0b · 286 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 673481754248da69b3e0f72d38f6e857b02053aaa862f9b37a32c243744884c3 · 44,323 bytes

Off-chain and mutable. This is what the launch served when we read it at 2026-09-25 04: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