1,140,615 launches on record
Coverage from 2 Sep 2026
Archive read 00:11 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

CUFFS

The creator took 65% of supply at launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.

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.

GYXsszHoN75Sbqt2L6pD6kc2YiGMkSKtoJjqDKyoxYNt Solscan pump.fun
findingThe creator bought its own bonding curve - 45 SOL, from the same wallet that created the token.
findingThe creator took 64.6% of the entire supply in the first block. Nothing visible on-chain today shows this - the float has since been spread across wallets.
findingThat purchase is what completed the curve: the token left the curve on the creator's own money.
noteTook 2 bonding curves outright. 91 SOL spent on curves. We hold no market trades for it in either direction, so what it did with the tokens afterwards is not on our record.
noteOnly 1.2 SOL of liquidity was in the pool just now.

At launch

Created2026-09-30 20:11 UTC
Creator236V1EWUMUtTa95k2vzX6tZfFasCDncSu44isSrHhqsn
Creator took64.6% of supply in the first block
Outside buyers38 distinct wallets, not counting the creator, bought on the bonding curve: 30 within the first 30s, 3 bundled into the creation block.
Graduated2 min after launch
Curve, read on chainNot read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch.
Creator soldnot while we watched
Recorded from4HzDXwV7aePudfkRQVb9hC… slot 452,068,292
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.

Order of events

Created2026-09-30 20:11:29 UTC
Slot 452,068,292, which is the chain's own clock for this moment.
Creation block3 wallets bought in the block the token was created in, before anyone outside could have seen it exist.
Thirty seconds in30 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-09-30 20:13:13 UTC +1m 44s
Confirmed: a PumpSwap pool was found for it.
Highest price seen2026-09-30 20:13:13 UTC +1m 44s
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 pictureNo other launch we hold a picture for used this one.
This tickerOn 3 launches from 3 creator wallets, including this one. See them →
This creator27 earlier launches, 1 confirmed graduated on chain, 1 with findings on record. See the creator's launches →

Who took the curve

One transaction bought 45 SOL of this curve, in the same batch of events as the launch, from the creator's own wallet. The wallet and the transaction →

That is the same transaction the token was created in: the launch and the purchase of its float are one signature.

Our launch and trade timestamps are both taken when the events are decoded, so events that arrived together carry the same one. That it was taken at or near launch is on the record; how many seconds after is not.

Pool

Liquidity1.2 SOL
Read from chain2026-10-01 02:42 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameLondon Hotel Arrest
DescriptionThe counterparty to the bandit: the police who took him at a London hotel four days after the hack.
Metadata heldsha256 7ec1ab0c120dbac3f87b74c469b878b90fd7d09058303b03b0c678e47358bb2c · 301 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 ed32b3c5ccf8396f45e338262cc749cd1c8bd95682a659a958084a2411f8c240 · 2,188,901 bytes

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