MOPEY
Also recorded, and not part of the finding above: this picture is on 2 other launches, all of them this same creator's, and this creator has 4,485 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, 15.2% of the launches whose picture we hold carry one only their own creator reused. 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.
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.
At launch
| Created | 2026-10-06 07:19 UTC |
| Creator | BAGSB9TpGrZxQbEsrEznv5jXXdwyP6AXerN8aVRiAmcv |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | unknown 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. |
| Graduated | not while we were watching |
| Curve on chain | Nothing 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 sold | not recorded - this venue's trades do not name the wallet |
| Recorded from | 3hxAu13srY8o5VhLHQ5qEw… slot 453,832,135
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | curve_buyers, unique_buyers, snap30_buyers, bundled_buyers - this launch's venue publishes trade events that do not name the wallet that traded, so no count of people can be taken from them - which is not zero and not a clean result. peak_price - we decoded no price for this launch at all - the column holds what we SAW, and a launch we stopped following has a peak that stops with us.
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. |
Seen before
| This picture | On 3 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 15.2% of the launches whose picture we hold carry one only their own creator reused. See them → |
| This ticker | On 2 launches from 2 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.3% wear one that more than one creator wallet has launched. See this ticker's page → |
| This creator | 4,485 earlier launches, 5 confirmed complete on chain. Across the archive, 71.7% of launches come from a creator with more than one launch on record. See the creator's launches → |
| Files shared with other wallets | Launches by this creator were made with files byte-identical to those of 744 other creator wallets, across 1,331 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. Across the archive, 57.8% of launches come from a creator linked to at least one other wallet this way. 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
| Name | Mopey Cat |
| Description | >Mopey Cat reflects every trader's mood swings in the crypto jungle. When the market dips, Mopey’s got your back! Join the community and let’s laugh our way through the emotional rollercoaster of trad |
| Metadata held | sha256 e7e4e3850c3332af5626fa5a451239ae75bb3cef7eea71b594de90ce8ed11c55 · 477 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 held | sha256 a18bb836e7c3ce9c86e633aaec44eaf843bbc7837453ac0fdd748624eee36175 · 4,932 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-06 07:20 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
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.