lockemup
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 3 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.8% 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.
At launch
| Created | 2026-10-02 20:08 UTC |
| Creator | 35eaDZXPzPfRPsFTVDJ9Kdmtzy1E2wEqM7fqPP916ACD |
| Creator took | 2.8% of supply in the first block |
| Outside buyers | 8 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: 3 within the first 30s, 1 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 | 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 while we watched |
| Recorded from | 49gYuf3GJe7MB5ue4ChibW… slot 452,713,383
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
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.
Order of events
| Created | 2026-10-02 20:08:49 UTC Slot 452,713,383, which is the chain's own clock for this moment. |
| Creation block | 1 wallet bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 3 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. |
| Highest price seen | 2026-10-02 20:10:25 UTC +1m 36s
3.381e-8 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 3 launches from 1 creator wallet, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 4 launches from 4 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. See this ticker's page → |
| This creator | 3 earlier launches, none of which reached a graduation threshold while we watched. See the creator's launches → |
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 | PRIVATE PROPERTY |
| Description | state?!!! |
| Metadata held | sha256 5a65ab407882e99ca39b432e3ab1393d288e0b596ba66c2c1c9ae4044973e2eb · 211 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 2813542956d60661ef0140277673592d2382ba2e21424fb42e0ed165998a346d · 254,822 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 20:08 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.