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 5 lists, or with Brand Protection at $79 a month for every list on every record. Watch this creator wallet: a free account is emailed the next time it launches. 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 59 other launches from 50 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.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-11-12 03:50 UTC |
| Creator | Dbu9xNNUvJ8pMcE2J74ya3XXShM84feP6CiTCgwZx2a |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 6 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: 6 within the first 30s, 6 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 | 0 min after launch |
| Curve on chain | Complete. We read the bonding curve account 3.0 days ago and it was finished. Checked 2026-11-12 04:00 UTC. |
| Creator sold | not while we watched |
| Recorded from | 3FhpiG4PE9Lt34HZ7irgWd… slot 468,380,727
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-11-12 03:50:39 UTC Slot 468,380,727, which is the chain's own clock for this moment. |
| Creation block | 6 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-11-12 03:50:42 UTC +3s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-11-12 03:50:42 UTC +3s
4.109e-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. |
| Thirty seconds in | 6 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. |
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 60 launches from 50 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 3 other launches, across 4 creator wallets in all. Across the archive, 33.4% of the launches whose document we hold carry one byte-identical to a different creator's. See them → |
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 | DeepSeek |
| Description | 1000x |
| Metadata held | sha256 d50ed9452e80304d6ee9d4dc0b23d06de9b9596895f433036ad5c5520cbc6290 · 347 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-13 03:51 UTC. |
| Picture held | sha256 46fee4a0b4791f5508fc9165e21ca066296fb25af90da569ab672df47c37db05 · 20,457 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-12 03:50 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.