PPAD
The curve completed 7s after launchRead from the launch record. What it means is the reader's to decide; we record what happened, not why.
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.
findingIt left the curve 7s after launch.
At launch
| Created | 2026-10-01 20:42 UTC |
| Creator | Cwc44v84Tf9ee4vaWwbBzKhfMEmFWQxWujPX9WKcCdJi |
| Creator took | 10.0% of supply in the first block |
| Outside buyers | 42 distinct wallets, not counting the creator, bought on the bonding curve: 42 within the first 30s, 15 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Not read. We have the feed's graduation event and have not confirmed it against the curve account itself. That is a gap in our checking, not a finding about this launch. |
| Creator sold | not while we watched |
| Recorded from | 5DNejBMGAYYDhKcFZMYWUg… slot 452,398,068
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-10-01 20:42:13 UTC Slot 452,398,068, which is the chain's own clock for this moment. |
| Creation block | 15 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-10-01 20:42:20 UTC +7s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-01 20:42:20 UTC +7s
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. |
| Thirty seconds in | 42 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. |
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. See them → |
| This ticker | On 4 launches from 4 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| 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 | 64.0 SOL |
| Read from chain | 2026-10-01 23:19 UTC, just now |
What this launch claimed to be
| Name | Pledge Capital |
| Metadata held | sha256 adc1c1c0ff83e1d0c055fee6af84ad1d96806a3d7f10563e3a0311949ddbd763 · 263 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 69f4f2dc5d786977ac07b20e9d5e6748e02dfca41a8be130da6974b1e7536df3 · 296,852 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 20:42 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.