2,302,443 launches on record
Coverage from 2 Sep 2026
Archive read 23 Oct 2026
Token lookup · free
Live API · with a key
Lists behind counts · Brand Protection

Shinubb

The curve completed 29s 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 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. 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.

8MnyAxqHiziEmmEaYAJHu6Ty2u7HCSPaRNtTxnXUpump Solscan pump.fun

Cite this record as: Chain of Title, Shinubb (Shinobi Inu), mint 8MnyAxqHiziEmmEaYAJHu6Ty2u7HCSPaRNtTxnXUpump, observed at creation 2026-10-23 12:39 UTC. Chain of Title, a register of Solana token launches recorded at creation. https://chainoftitle.org/t/8MnyAxqHiziEmmEaYAJHu6Ty2u7HCSPaRNtTxnXUpump

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 29s after launch.
noteThe creator sold while we were watching.
noteOnly 0.0 SOL of liquidity was in the pool just now.

At launch

Created2026-10-23 12:39 UTC
CreatorE9nNyJocDxETTh7tcoXPAPpUKtYm6ZEYpPWWWo9ByzaQ
Creator took0.4% of supply in the first block
Outside buyers34 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: 10 within the first 30s, 0 in the very same block the token was created in.
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 soldyes
Recorded fromZ52SCXtZt6hNMD76rp5yS5… slot 460,446,133
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-23 12:39:23 UTC
Slot 460,446,133, which is the chain's own clock for this moment.
Creation blockNo wallet bought in the block the token was created in.
Curve completed2026-10-23 12:39:52 UTC +29s
Confirmed: a PumpSwap pool was found for it.
Thirty seconds in10 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-23 12:40:36 UTC +1m 13s
4.382e-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 creator14 earlier launches. All 3 that reached the graduation threshold on our feed were read on chain, and none had completed. Across the archive, 70.1% of launches come from a creator with more than one launch on record. See the creator's launches →

Pool

Liquidity0.0 SOL
Read from chain2026-10-24 01:39 UTC, just now

What this launch claimed to be

The picture this launch published at birth
NameShinobi Inu
Description🐕🥷🔥 Shinobi Inu ($SHINU) Not your average Shiba. Not your average ninja. Meet Shinobi Inu — the legendary meme dog who mastered the art of chakra! 🍥 Ninja skills unlocked. 💙 Rasengan fully charged. 🐕 Shiba energy activated. 🔥 9999+ Chakra. Zero Braincells. One Ninja. One Dog. Infinite Memes! $SHINU — The Ninja Dog Has Awakened! 🚀
Metadata heldsha256 b0904937416b6cfd5de34a1a0a50d10e5c6f2ba2d404c30030e145433c1baa0c · 574 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 3a22b7bc55a8d0452356d6be3c909dce2432d3c8754724cccd2ef087cb4fff9f · 479,587 bytes

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