1,488,186 launches on record
Coverage from 2 Sep 2026
Archive read 21:53 UTC today
Token lookup · free
Live API · with a key
Lists behind counts · Pro

BUNKER

No finding either wayWe watched this launch and ran the launch-record tests on it: what the creator took in the first block, how many wallets bought on the curve, how fast the curve filled, and whether a single buy completed it. None of them fired, and a marker is one of those tests firing. We still do not head this record 'no markers found': that line is kept for launches whose curve we watched fill slowly with at least thirty outside buyers, and this one did not complete a curve at all. Those tests read this launch's own first blocks only. What it shares with other launches is counted below and is not part of this answer. Neither endorsed nor accused.

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.

DxPVKGxwJuQLrWuJZbsza4pdBdsCAaDupT31LeMqpump Solscan pump.fun

At launch

Created2026-10-06 18:03 UTC
CreatorGqs3SS1R4gmeDbLoPYkEFE5e3oxV7FkT6RQcRswTskUQ
Creator took4.1% of supply in the first block
Outside buyers0 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: 0 in the very same block the token was created in.
Graduatednot while we were watching
Curve on chainNothing to confirm. This launch never reached a graduation threshold while we watched, so there was no completion to check against the curve account. Most tokens end this way, and it is not a finding about them.
Creator soldnot while we watched
Recorded from5uWBwhMqpbyoqZBxk4HTYh… slot 453,976,413
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us.
Not recordedsnap30_buyers - no thirty-second snapshot was taken, and that snapshot is meaningful only for an observed launch.
Each is unknown rather than zero. An unknown never certifies a launch and never counts against one; it is the record declining to state something. The column names link to their full entries in the published schema, which is where the rest of the reason is written down.

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-06 18:03:44 UTC
Slot 453,976,413, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Highest price seen2026-10-06 18:16:26 UTC +12m 41s
5.744e-8 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 27 launches from 25 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, 86.4% wear one that more than one creator wallet has launched. See this ticker's page →

Pool

We have no pool balance for this token that we can date, so none is quoted. That is a gap in our reading coverage and says nothing about the launch record above, which does not depend on it.

What this launch claimed to be

The picture this launch published at birth
NameBUNKER
DescriptionBrought his own vault. Still checks the lock seventeen times. 🐢🔐
Metadata heldsha256 cf2d885885e06fb4254376aab7483d933ffa181e09caca4934828fa5a8f5fe94 · 364 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 0bfd609f36491cdbb52f1b1137563a48600404fa4e91320d107a8cb827ccf12f · 530,082 bytes

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