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

Leverhedge

The curve completed 2s 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 1 other launch. 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.

FWatMYieKhRuJ1yuTcmVG1njRhZWwqHwjR11pBympump Solscan pump.fun

Cite this record as: Chain of Title, Leverhedge, mint FWatMYieKhRuJ1yuTcmVG1njRhZWwqHwjR11pBympump, observed at creation 2026-10-30 23:41 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/FWatMYieKhRuJ1yuTcmVG1njRhZWwqHwjR11pBympump

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 2s after launch.

At launch

Created2026-10-30 23:41 UTC
CreatorH6KAJ89odHVqdUTMTxioH9BNLqrMtTfpTVWFw5vAwhYE
Creator took0.1% of supply in the first block
Outside buyers18 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: 18 within the first 30s, 18 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.
Graduated0 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 from63YQBjnEsiqaJgKjG1tPdr… slot 463,473,647
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-30 23:41:12 UTC
Slot 463,473,647, which is the chain's own clock for this moment.
Creation block18 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Curve completed2026-10-30 23:41:14 UTC +2s
Confirmed: a PumpSwap pool was found for it.
Thirty seconds in18 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-10-30 23:42:21 UTC +1m 09s
1.486e-6 SOL per token. Reported by a third-party price feed with no trade witnessed, which is a materially weaker claim than a decoded one. 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 30 launches from 21 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.4% wear one that more than one creator wallet has launched. See this ticker's page →

Pool

Liquidity313.2 SOL
Read from chain2026-10-31 04:45 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameLeverhedge
DescriptionTrade memes, hedge your exposure with leverage
Metadata heldsha256 5b5c92fbda33c20c66c5560584e75be9453af1d56bec84acacaeb431db1d8a20 · 244 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 a044894a47ca0b6bbaba025e9f7c60b30c14118a3026a5665d2a25d163d314f9 · 256,873 bytes

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