PUMP
The curve completed 29s 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 29s after launch.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-18 15:00 UTC |
| Creator | 6ePbEvTDFGPembAtY1vwLF4CWbTWKFisUE2G2k53tHHw |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 32 distinct wallets, not counting the creator, bought on the bonding curve: 33 within the first 30s, 4 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 | 3zqj2XQtNsq1cQj2sEJW4F… slot 448,117,711
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-18 15:00:35 UTC Slot 448,117,711, which is the chain's own clock for this moment. |
| Creation block | 4 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Highest price seen | 2026-09-18 15:00:35 UTC
2.796e-8 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. |
| Curve completed | 2026-09-18 15:01:04 UTC +29s Confirmed: a PumpSwap pool was found for it. |
| Thirty seconds in | 33 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 5 launches from 5 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 861 launches from 510 creator wallets, including this one. See them → |
| This document | Byte-identical to 1 other launch's metadata document. See them → |
| This creator | 1,009 earlier launches, 38 confirmed graduated on chain, 3 with findings on record. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 317 other creator wallets, across 530 shared artifacts, each matched by hash. The linkage sits in a component too large for this record to state as one group; the record states that exclusion. See the linked wallets → |
Pool
| Liquidity | 0.0 SOL |
| Read from chain | 2026-09-18 22:51 UTC, just now |
What this launch claimed to be
| Name | respect the pump |
| Description | - |
| Metadata held | sha256 3101a72ad843b6ae5a2fd17cbd8b8becfc3c0c64b8f8a40dd59098ca79a2c43b · 368 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 43006592578edcdc1216975654f0c821c106e47fdf3698097d49a509ba9bd4ac · 3,678 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-18 15:00 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.