www
The curve completed 4s 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 4s after launch.
noteOnly 9.0 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 03:04 UTC |
| Creator | BcYPd7Ym3mnt5996JDkxaQodfZ3YcW3Zevx3yjm3mZqD |
| Creator took | 1.8% of supply in the first block |
| Outside buyers | 76 distinct wallets, not counting the creator, bought on the bonding curve: 77 within the first 30s, 14 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read 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 | 3r1H61kj6H5eXHLfeDWM5h… slot 452,483,603
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 03:04:33 UTC Slot 452,483,603, which is the chain's own clock for this moment. |
| Creation block | 14 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-10-02 03:04:37 UTC +4s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 03:04:37 UTC +4s
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 | 77 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 3 launches from 3 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 219 launches from 175 creator wallets, including this one. See them → |
Pool
| Liquidity | 9.0 SOL |
| Read from chain | 2026-10-02 12:47 UTC, just now |
What this launch claimed to be
| Name | worldwideweb |
| Metadata held | sha256 4288aa2f96b0f91bd3d926af6b4224444e212f93b88a7479db6b661c713a6712 · 271 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 86331b6c2de54487eb4c720faa3704b4b8838f81169cce18cf66757767a2bae4 · 16,374 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 03:04 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.