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

犬神

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.

Also recorded, and not part of the finding above: this picture is on 13 other launches from 13 creator wallets in all, and this creator has 14 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, 44.4% of the launches whose picture we hold carry one a different creator also used. 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.

DuvXAuNsiMtZYNX2wmsMfT1ZSZWw8URsrajuzF2dpump Solscan pump.fun

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 sold while we were watching.

At launch

Created2026-10-03 06:36 UTC
Creator9T9SLkqqWYLABNnsKK8oz1p6LUTk1WkZxRBi3GQtPRAN
Creator took0.4% 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 within the first 30s, 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 soldyes
Recorded from4jgfe2qn1qfTRuDkouFG5E… slot 452,854,352
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-03 06:36:34 UTC
Slot 452,854,352, 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-03 06:36:34 UTC
2.816e-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.
Thirty seconds inNo buyer, 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.

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 14 launches from 13 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them →
This tickerOn 49 launches from 44 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. See this ticker's page →
This creator14 earlier launches, none of which reached a graduation threshold while we watched. See the creator's launches →
Files shared with other walletsLaunches by this creator were made with files byte-identical to those of 14 other creator wallets, across 18 shared files, each matched by its sha256 fingerprint. Sharing a file establishes that the same file was used, never that the same person used it. Following those shared files outward reaches a group so large that this register stops being able to tell individual hands apart inside it, so it does not name the group or state a size. That limit is published with the method rather than left for a reader to discover. See the linked wallets →

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
NameInugami
DescriptionA community-driven token built for transparent, verifiable on-chain research and open governance.
Metadata heldsha256 47dc729fd78a2b1d4f1403bb7c09a761698a6fe4da85301d5f567e0bf0b05975 · 572 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 e1cd9ca86689c655e0bbd384e2e80ae06a2582550cfda698fa7ab736659ad4ba · 44,271 bytes

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