1.0%of supply taken by the creator in the first block
1,204outside wallets bought on the bonding curve
Yesreached a graduation threshold while we watched
24launches carry this ticker, from 20 creator wallets4other launches declared this same launch document, byte for byte
5other launches used this exact picture file
Checked at birth, no markers foundWe watched this launch and ran every LAUNCH-RECORD test we have on it. None fired: the creator kept 1.0%, 1,204 outside wallets bought on the curve, the curve took longer than a minute to fill, and no single wallet took it. These tests read this launch's own first blocks and nothing else. What this launch shares with other launches - the same picture, the same document, the same creator - is counted separately, below, and is not part of this answer.
Also recorded, and not part of the finding above: this picture is on 5 other launches from 6 creator wallets in all. 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.2% of the launches whose picture we hold carry one a different creator also used. They are listed under Seen before, further down this page.
At launch
| Created | 2026-11-09 04:20 UTC |
| Creator | 3ocgvoBZqzsJZsediLUdHaQySvoZsud7XRLQeYXz4xvG |
| Creator took | 1.0% of supply in the first block |
| Outside buyers | 1,204 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: 121 within the first 30s, 4 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 | 1.2 h 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 | 4qUGVmk1TJTDZUaKwdp7nd… slot 467,181,291
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-11-09 04:20:56 UTC Slot 467,181,291, which is the chain's own clock for this moment. |
| Creation block | 4 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 121 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-11-09 05:32:53 UTC +1h 11m 57s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-11-09 06:45:27 UTC +2h 24m 31s
8.617e-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 picture | On 6 launches from 6 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.2% of the launches whose picture we hold carry one a different creator also used. See them → |
| This ticker | On 24 launches from 20 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, 89.5% wear one that more than one creator wallet has launched. See this ticker's page → |
| This document | The same launch document, byte for byte, as 4 other launches, across 5 creator wallets in all. Across the archive, 33% of the launches whose document we hold carry one byte-identical to a different creator's. See them → |
| Files shared with other wallets | Launches by this creator were made with files byte-identical to those of 5 other creator wallets, across 3 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, 64% of launches come from a creator linked to at least one other wallet this way. See the linked wallets → |
Pool
| Liquidity | 60.1 SOL |
| Read from chain | 2026-11-11 20:15 UTC, just now |
What this launch claimed to be
| Name | hoss |
| Description | Launched on discord.gg/uxento |
| Metadata held | sha256 261617d472bfacb545eecf5c6f551fbd92a7119a46a705815df89a058170ee85 · 309 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-11-10 04:21 UTC. |
| Picture held | sha256 1659c38df845995f5c7b9b70769ce0d4e49be7a3fd5f1783f653703cbf092ea5 · 19,439 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-09 04:20 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.