🚀🚀
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.
noteOnly 0.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-01 06:32 UTC |
| Creator | BTUTSZiiGRUHrLEkNxNt917P7MHSA2eZWgTpErinDjbH |
| Creator took | 0.2% of supply in the first block |
| Outside buyers | 38 distinct wallets, not counting the creator, bought on the bonding curve: 4 within the first 30s, 0 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 | 5g4CaPhjMnHSGN2ftQWGBc… slot 452,207,586
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 06:32:13 UTC Slot 452,207,586, which is the chain's own clock for this moment. |
| Creation block | No wallet bought in the block the token was created in. |
| Curve completed | 2026-10-01 06:32:20 UTC +7s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-01 06:32:41 UTC +28s
1.565e-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 | 4 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 14 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 14 launches from 5 creator wallets, including this one. See them → |
| This document | Byte-identical to 8 other launches' metadata document. See them → |
| This creator | 808 earlier launches, 35 confirmed graduated on chain, 1 with findings on record. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 15 other creator wallets, across 21 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-10-01 20:33 UTC, just now |
What this launch claimed to be
| Name | DUMP.FUN |
| Metadata held | sha256 9242c21bd3d0059093e56bf453a9aa686957cf7383bc3c3985903e7f2144901a · 194 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 d5e775493d96c27125469a8802039223d5c9004ef07ea61e2fd5e46cb24dd17f · 209,498 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-01 06:32 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.