1,923,003 launches on record
Coverage from 2 Sep 2026
Archive read 03:15 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

Sevda

The curve completed 33s after launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.

Also recorded, and not part of the finding above: this picture is on 51 other launches, all of them this same creator's, and this creator has 113 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. Across the archive, 14.3% 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.

4bhh5R5cDxG6ACfQxuAc5WM9kkXLMEUrfZDsL6C5pump Solscan pump.fun

Cite this record as: Chain of Title, Sevda, mint 4bhh5R5cDxG6ACfQxuAc5WM9kkXLMEUrfZDsL6C5pump, observed at creation 2026-10-14 16:51 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/4bhh5R5cDxG6ACfQxuAc5WM9kkXLMEUrfZDsL6C5pump

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.

findingIt left the curve 33s after launch.
noteThe creator sold while we were watching.
noteOnly 0.0 SOL of liquidity was in the pool just now.

At launch

Created2026-10-14 16:51 UTC
Creator3nknJYKTMekjY6EGoRL8CaujXPHiD4DiRfYUUwy3P78U
Creator took1.7% of supply in the first block
Outside buyers33 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: 3 within the first 30s, 0 in the very same block the token was created in.
Graduated1 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 soldyes
Recorded from4viADGbnDoiNh83sXtfTSP… slot 456,911,155
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-14 16:51:31 UTC
Slot 456,911,155, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Thirty seconds in3 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-14 16:52:04 UTC +33s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-10-14 16:54:10 UTC +2m 39s
6.433e-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 52 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 14.3% of the launches whose picture we hold carry one only their own creator reused. See them →
This tickerOn 54 launches from 1 creator wallet, 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.4% wear one that more than one creator wallet has launched. See this ticker's page →
This documentThe same launch document, byte for byte, as 53 other launches, 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 creator113 earlier launches. 28 reached the graduation threshold on our feed; we have read the curve account for 27, and 27 had not completed. Across the archive, 69.9% of launches come from a creator with more than one launch on record. See the creator's launches →

Pool

Liquidity0.0 SOL
Read from chain2026-10-15 06:52 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameSevda
Metadata heldsha256 818d34c686b92bc0352429a92eca1142b7ad4142c48e0e82a38787870a44e125 · 188 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 5f70da232def5326b98d8ee9cfb980ed6917383b89cbfa625e3fcd54431d1fcc · 42,497 bytes

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