What this launch shares with other launches
Free on this page: that each of these exists, and how many. The list behind a count, meaning which launches, which wallets and the transaction for each, opens with a free account for five lists, or with Brand Protection at $79 a month for every list on every record. This one launch can also be kept as a $49 document with its identical-file and creator lists, further down this page.
Its own first blocks
Also recorded, and not part of the finding above: this picture is on 1 other launch from 2 creator wallets in all, and this creator has 2 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, 56.5% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.
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-09-10 16:52 UTC |
| Creator | GzBp8NtiSa6J9HRd6R7wWxbppPawGRUASbpxYVSeDvqk |
| Creator took | 1.4% 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: 180 within the first 30s, 5 in the very same block the token was created in - a block is one batch of transactions, so those buys and the creation were confirmed together. |
| Graduated | 11 min after launch |
| Curve on chain | Not 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 sold | not while we watched |
| Recorded from | 5DRjFHmoJ6X3mWfmQncUeP… slot 445,933,964
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
| Not recorded | curve_buyers - its trade rows had already been sampled at finalize or pruned by retention before anything counted them, so any count over the survivors would be a floor rather than a measurement.
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. |
Order of events
| Created | 2026-09-10 16:52:04 UTC Slot 445,933,964, which is the chain's own clock for this moment. |
| Creation block | 5 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 180 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 completed | 2026-09-10 17:02:34 UTC +10m 30s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-10 17:04:58 UTC +12m 54s
1.069e-6 SOL per token.
Source not recorded, which is every row written before 2026-09-10 - never that the peak was
unsourced.
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 picture | On 2 launches from 2 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.5% of the launches whose picture we hold carry one a different creator also used. See them → |
| This document | The same launch document, byte for byte, as 1 other launch, across 2 creator wallets in all. Across the archive, 33.3% of the launches whose document we hold carry one byte-identical to a different creator's. See them → |
| This creator | 2 earlier launches, none of which reached a graduation threshold while we watched. Across the archive, 70.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 2 other creator wallets, across 5 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, 63.7% of launches come from a creator linked to at least one other wallet this way. See the linked wallets → |
Pool
| Liquidity | 2.2 SOL |
| Read from chain | 2026-11-14 05:23 UTC, just now |
What this launch claimed to be
| Name | suitdog |
| Description | Launched on discord.gg/uxento |
| Metadata held | sha256 cc9ff75f028f1f64a7903f509eede1a99d76de828e0ed3865ba413a125a244e6 · 297 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. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-09-17 16:52 UTC. |
| Picture held | sha256 f4d17e3afa654cfb3426b2964de07b664a2269de1c9708fb9f5316e60d7cca2c · 6,928 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-10 16:52 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.