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

BLASTAR

Checked at birth, no markers foundWe watched this launch and ran every LAUNCH-RECORD test we have on it. None fired: the creator kept 3.5%, 237 outside wallets bought on the curve, the curve took longer than a minute to fill, and no single wallet took it. These tests read this launch's own first blocks and nothing else. What this launch shares with other launches - the same picture, the same document, the same creator - is counted separately, below, and is not part of this answer.

Also recorded, and not part of the finding above: this picture is on 1 other launch, all of them this same creator's, and this creator has 1 other launch 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. Across the archive, 14.6% of the launches whose picture we hold carry one only their own creator reused. 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.

DTZJdzvBkmfVXv1JhL6wUC68k2ktnCXHYG6dz4ACS984 Solscan pump.fun

Cite this record as: Chain of Title, BLASTAR (Blastar), mint DTZJdzvBkmfVXv1JhL6wUC68k2ktnCXHYG6dz4ACS984, observed at creation 2026-10-07 13:28 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/DTZJdzvBkmfVXv1JhL6wUC68k2ktnCXHYG6dz4ACS984

At launch

Created2026-10-07 13:28 UTC
Creator3wLGNGAwEFxwhmFVDwFNN7LdebJj6HcsWMDsmq8mjn5L
Creator took3.5% of supply in the first block
Outside buyers237 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: 97 within the first 30s, 7 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.
Graduated6 min after launch
Curve on chainNot re-read, deliberately: the pool is the confirmation. Migration empties a completed curve into its pool, so the pool's existence - recorded on this page - proves what the curve account would. Curve reads are spent where no pool answers.
Creator soldnot while we watched
Recorded from2S8vSoLmTfquoGU5dHJhvY… slot 454,236,491
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-10-07 13:28:50 UTC
Slot 454,236,491, which is the chain's own clock for this moment.
Creation block7 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in97 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 completed2026-10-07 13:34:33 UTC +5m 43s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-10-07 13:34:33 UTC +5m 43s
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 pictureOn 2 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 14.6% of the launches whose picture we hold carry one only their own creator reused. See them →
This tickerOn 61 launches from 39 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 documentThe same launch document, byte for byte, as 1 other launch, all of them this same creator's. Across the archive, 11.2% of the launches whose document we hold carry one only their own creator reused. See them →
This creator1 earlier launch, none of which reached a graduation threshold while we watched. Across the archive, 70.4% of launches come from a creator with more than one launch on record. See the creator's launches →

Pool

Liquidity45.2 SOL
Read from chain2026-10-11 15:39 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameBlastar
Metadata heldsha256 92b0464044dc43f27cb866edd391c281ec6b1ac49c84c4b42f6497c4d2efd1bd · 288 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 91517c9909c40af1a95869a3eb06d0bbe8113551a11b1cc4815aa28862602a2b · 401,419 bytes

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