3,400,377 launches on record
Coverage from 2 Sep 2026
Archive read 00:12 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

Boomer

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.

A record of what this launch was at birth, read from the Solana chain. We did not record its creation transaction, so these figures rest on our observation at the time rather than on a citation you can follow. Not a prediction and not advice.

6PipCS2EJ5fH9boGbJxStcsRpNh5WbN3dSZycLWPdbi4 Solscan pump.fun

Cite this record as: Chain of Title, Boomer, mint 6PipCS2EJ5fH9boGbJxStcsRpNh5WbN3dSZycLWPdbi4, observed at creation 2026-09-03 00:02 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/6PipCS2EJ5fH9boGbJxStcsRpNh5WbN3dSZycLWPdbi4

At launch

Created2026-09-03 00:02 UTC
Creator8V73BhS4DgpMW8LZreh78VZVUpvCteMyLHviProg4Tbj
Creator took0.0% of supply in the first block
Outside buyers838 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: 116 within the first 30s, 6 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 fromNot recorded. This launch predates our keeping the creation transaction (2026-09-09), and its trade rows had been pruned by retention before the backfill could recover the signature from them. The figures above stand on our own observation alone, which is weaker than a citation, and we would rather say so than leave the gap unmarked.

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.

Several launches in one matter

A pack of 10 of these documents is $200, redeemed one launch at a time whenever you find the next one. You get a code by email; it does not expire.

Order of events

Created2026-09-03 00:02:51 UTC
Creation block6 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Highest price seen2026-09-03 00:02:51 UTC
3.452e-7 SOL per token. Source not recorded, which is every row written before 2026-09-10 - never that the peak was unsourced. A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not here.
Thirty seconds in116 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.

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 278 launches from 211 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.4% 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
NameBoomer
Metadata heldsha256 e9d510db1e957493a593a4546399a101c19fbd1fbe345fb4a09fa43c393d7bd7 · 336 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 507b5fa08205672b082b2618d054ffebb7f3e7005035c9fd03b8af8a02657880 · 11,070 bytes

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