Minecraft
The curve completed 24s 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 24s after launch.
noteOnly 3.7 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 19:36 UTC |
| Creator | AmbWycQajhY9drWQiysyy6kzW4iD2JwhhYfVLp6GHRyz |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 165 distinct wallets, not counting the creator, bought on the bonding curve: 165 within the first 30s, 0 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 | 3V19rk451Dn7jRR3fW81pp… slot 452,706,044
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 19:36:01 UTC Slot 452,706,044, 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-02 19:36:25 UTC +24s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-10-02 19:36:25 UTC +24s
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 | 165 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 7 launches from 7 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 128 launches from 114 creator wallets, including this one. See them → |
| This document | Byte-identical to 2 other launches' metadata document. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 2 other creator wallets, across 2 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 | 3.7 SOL |
| Read from chain | 2026-10-03 01:31 UTC, just now |
What this launch claimed to be
| Name | Minecraft |
| Metadata held | sha256 0748deafd29c16c7dde1ae9193b35ed9f35bf7677f2e2fc3140e84b5382e9b7b · 299 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 f170fcc2b3ab0295274c1e0b00db66a72007986544db19eadc7acd49b08450fb · 13,181 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 19:36 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.