PANDORA
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.
noteOnly 2.1 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 05:34 UTC |
| Creator | PkJLg8a2HN44ZgLiBBuiZFXv1RD5B9qhNYyjzAM6jo8 |
| Creator took | 4.5% of supply in the first block |
| Outside buyers | 15 distinct wallets, not counting the creator, bought on the bonding curve: 13 within the first 30s, 13 bundled into the creation block. |
| Graduated | 55 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 13.6 h ago and it was finished. Checked 2026-10-02 06:31 UTC. |
| Creator sold | not while we watched |
| Recorded from | 3UrLBPacPi6s4G4fDDGf2H… slot 452,517,145
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 05:34:29 UTC Slot 452,517,145, which is the chain's own clock for this moment. |
| Creation block | 13 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 13 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 06:29:54 UTC +55m 26s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-10-02 06:29:54 UTC +55m 26s
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 | No other launch we hold a picture for used this one. |
| This ticker | On 12 launches from 10 creator wallets, including this one. See them → |
Pool
| Liquidity | 2.1 SOL |
| Read from chain | 2026-10-02 20:08 UTC, just now |
What this launch claimed to be
| Name | Pandora |
| Description | Pandora was originally a collection of 10,000 avatars or "replicants", bound to the first tokens built on ERC404, an experimental token standard enabling persistent liquidity and semi-fungibility for Ethereum NFTs. |
| Metadata held | sha256 51cd3f7e2263d13e9265ef8ad8d440b7c89e070048383f05fddeea2c17593725 · 428 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 b5cd082a8cdff9eeea41d17c39d61549f3d71041ef37453eab0aac15c0610b14 · 1,820 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 05:34 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.