2,325,483 launches on record
Coverage from 2 Sep 2026
Archive read 03:58 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

ELIZABETH

The creator took 40% of supply at 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 2 other launches. 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.

Biiv46yBzZwwdg3HvYQ52yPXmnMb5EnF8dboTx2qpump Solscan pump.fun

Cite this record as: Chain of Title, ELIZABETH (Why would I deceive you?), mint Biiv46yBzZwwdg3HvYQ52yPXmnMb5EnF8dboTx2qpump, observed at creation 2026-10-24 00:32 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/Biiv46yBzZwwdg3HvYQ52yPXmnMb5EnF8dboTx2qpump

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.

noteThe creator took 40.2% of supply at launch.

At launch

Created2026-10-24 00:32 UTC
Creator4z4fptrKJU9k25XKUj1HHdC42TMDTdnv2oHDCSU2FcVx
Creator took40.2% of supply in the first block
Outside buyers575 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: 178 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.
Graduated12 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 from2dcmPnihSWs7Bg8aXRFeax… slot 460,647,899
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.

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-10-24 00:32:25 UTC
Slot 460,647,899, which is the chain's own clock for this moment.
Creation block6 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in178 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-24 00:44:38 UTC +12m 13s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-10-24 02:31:25 UTC +1h 59m 00s
3.089e-6 SOL per token. Recovered from the prices we still held when the launch was finalised, rather than witnessed as it happened. 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 tickerOn 1,435 launches from 510 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, 88.1% wear one that more than one creator wallet has launched. See this ticker's page →

Pool

Liquidity189.5 SOL
Read from chain2026-10-24 06:59 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameWhy would I deceive you?
Metadata heldsha256 54c5699ca7f4c238183fa43308a1ab754ba090778df53be2ee6d4f0c7f81aa37 · 410 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 591dbb3e427800a6d4922ca2f27fb469412c434493da4cefddd3445f84d74808 · 16,608 bytes

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