$SLJK
No finding either wayWe watched this launch. It matches none of the patterns we record, and it does not meet every criterion for a record with no markers. Neither endorsed nor accused.
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.
noteThe creator sold while we were watching.
noteOnly 0.1 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 08:07 UTC |
| Creator | 8DcYT1eF4U4GU8KiEA8MxEC4ZLoWc57kiCwKRFijDtXi |
| Creator took | 0.3% of supply in the first block |
| Outside buyers | 25 distinct wallets, not counting the creator, bought on the bonding curve: 2 within the first 30s, 0 bundled into the creation block. |
| Graduated | 2 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 8.4 h ago and it was finished. Checked 2026-10-02 08:31 UTC. |
| Creator sold | yes |
| Recorded from | 3mVSJ5UCj218Dhq8vL5SYt… slot 452,551,578
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-02 08:07:40 UTC Slot 452,551,578, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Thirty seconds in | 2 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-10-02 08:09:30 UTC +1m 50s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-10-02 08:11:32 UTC +3m 52s
1.302e-6 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 879 launches from 259 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 891 launches from 260 creator wallets, including this one. See them → |
| This document | Byte-identical to 584 other launches' metadata document. See them → |
| This creator | 19 earlier launches, 0 confirmed graduated on chain. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 1 other creator wallet, across 3 shared artifacts, each matched by hash. Together they sit in a linked group of 2 creator wallets. See the linked wallets → |
Pool
| Liquidity | 0.1 SOL |
| Read from chain | 2026-10-02 16:52 UTC, just now |
What this launch claimed to be
| Name | Soljack |
| Description | Solana wojak |
| Metadata held | sha256 62cb2491cd45f8f5579b90efc3ee20baf622bd41423b4e9bcf71b4d02a460d7d · 204 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 385c95f738667c7bb0224d04431b15d8a9f90c36b35d44ee6e75b6db75925e99 · 74,395 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 08:07 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.