Launch record · observed at creation 2026-11-13 03:06 UTC
JENSENSWAN
Jensen Swan
Also recorded, and not part of the finding above: this picture is on 8 other launches from 6 creator wallets in all, and this creator has 119 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.4% 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-13 03:06 UTC |
| Creator | tHrKD2HCzaME3cWzryczK7sKAsofdQdXd4jmDawbKpx |
| 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 | in the same batch of events as the launch |
| Curve on chain | Not read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch. |
| Creator sold | not recorded - this venue's trades do not name the wallet |
| Recorded from | 2sMntGJVVMPmDWrsHEi6wX… slot 468,769,783
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. |
Order of events
| Created | 2026-11-13 03:06:11 UTC Slot 468,769,783, which is the chain's own clock for this moment. |
| Curve completed | 2026-11-13 03:06:11 UTC Confirmed against the venue's own completion state. |
Times are the blocks' own timestamps, to the second: events in the same block share one, so their order within a block is not shown here.
Seen before
| This picture | On 9 launches from 6 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. Across the archive, 56.4% of the launches whose picture we hold carry one a different creator also used. See them → |
| This creator | 119 earlier launches, 74 confirmed complete on chain, 48 with findings on record. 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 56 other creator wallets, across 47 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.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 | Jensen Swan |
| Metadata held | sha256 2fe30bc5a4df09cdace38ec1929886260bf2873da5448f238a0b3714703b9514 · 269 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 4c9105c971db23bc99f3422eb97502a22e6255286ead5105705974fdb2505313 · 18,716 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-13 03:06 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.