Also recorded, and not part of the finding above: this picture is on 1 other launch from 2 creator wallets in all. 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-12 18:47 UTC |
| Creator | FerLhxuxR7v8v3dW7pBnvAxnNkPSv2JTo8Pv1L1FTrGa |
| Creator took | 9.1% of supply in the first block |
| Outside buyers | 422 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: 10 within the first 30s, 8 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 | 42 min after launch |
| Curve 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 | not while we watched |
| Recorded from | 5bK1XcVYsTdfp4SDZSnG6y… slot 468,630,983
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-11-12 18:47:21 UTC Slot 468,630,983, which is the chain's own clock for this moment. |
| Creation block | 8 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 10 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-11-12 19:29:26 UTC +42m 05s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-11-12 19:29:26 UTC +42m 05s
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 2 launches from 2 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 document | The same launch document, byte for byte, as 1 other launch, across 2 creator wallets in all. Across the archive, 33.2% of the launches whose document we hold carry one byte-identical to a different creator's. See them → |
| Files shared with other wallets | Launches by this creator were made with files byte-identical to those of 1 other creator wallet, across 3 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 of 2 creator wallets in all. 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
| Liquidity | 3.6 SOL |
| Read from chain | 2026-11-13 04:37 UTC, just now |
What this launch claimed to be
| Name | PAD2 |
| Description | Your all in one launchpad |
| Metadata held | sha256 a7ed82103b8293caac3b261b69c523bd9554d1a74628213310d34afef788b8f7 · 313 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 052c1bb6e0df8caee6988611ece0fd4b9783f9b90436b05a125860c0c4a5844f · 3,448 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-11-12 18:47 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.