>_
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 6.7 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 18:09 UTC |
| Creator | HJSTQEQB9MHuFKfFrRVtyG9QKMEVheYn8SiiJuK42x2n |
| Creator took | 2.8% of supply in the first block |
| Outside buyers | 990 distinct wallets, not counting the creator, bought on the bonding curve: 6 within the first 30s, 1 bundled into the creation block. |
| Graduated | 16 min after launch |
| Curve, read 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 | yes |
| Recorded from | 3SsvSxi5ZPa9JyNJocfeEm… slot 452,686,769
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 18:09:34 UTC Slot 452,686,769, 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 | 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. |
| Curve completed | 2026-10-02 18:25:47 UTC +16m 13s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 18:25:47 UTC +16m 13s
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. |
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 24 launches from 23 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 69 launches from 63 creator wallets, including this one. See them → |
Pool
| Liquidity | 6.7 SOL |
| Read from chain | 2026-10-03 00:59 UTC, just now |
What this launch claimed to be
| Name | Agent.exe |
| Metadata held | sha256 077bdb8366101e128fb861f6f13dd0ee7e590f1e1d460d1de14757bfafeb92c4 · 392 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 f3c6a08a44007c4f9c8bbf6016d2037ad8a271ba380662856d09c2a63817b73e · 269,637 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 18:09 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.