BUNMORTY
The curve completed 11s 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 11s after launch.
noteOnly 4.4 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 19:09 UTC |
| Creator | C2TCWLhbnxt68bcRQbEEhQoRFjbVKmRajgWfKqatVfFE |
| Creator took | 0.0% of supply in the first block |
| Outside buyers | 56 distinct wallets, not counting the creator, bought on the bonding curve: 56 within the first 30s, 10 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 | win7QM637PNzw2zMR9DToq… slot 451,731,535
The transaction this record was decoded from. Every figure above is in it. Fetch it and check us. |
Order of events
| Created | 2026-09-29 19:09:21 UTC Slot 451,731,535, which is the chain's own clock for this moment. |
| Creation block | 10 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-29 19:09:32 UTC +11s Confirmed: a PumpSwap pool was found for it. |
| Thirty seconds in | 56 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. |
| Highest price seen | 2026-09-29 19:15:12 UTC +5m 52s
0.000e+0 SOL per token.
Source not recorded, which is every row written before 2026-09-10 - never that the peak was
unsourced.
A peak only ratchets, so read it as a floor: it is what we saw, and a spike between observations is not
here. |
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 | No other launch we hold a picture for used this one. |
| This ticker | On 2 launches from 2 creator wallets, including this one. See them → |
Pool
| Liquidity | 4.4 SOL |
| Read from chain | 2026-10-01 06:35 UTC, just now |
What this launch claimed to be
| Name | Bundle Morty |
| Description | too small for the armor. too brave to care. $BUNMORTY |
| Metadata held | sha256 f66216c2ec708a5c2787529612af1805d364ee8a80987fc9cb146e3e798f2b04 · 403 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. |
| Document re-read | Byte-identical to the launch-time capture when re-read 2026-09-30 19:10 UTC. |
| Picture held | sha256 ef6e35aa5af174a6a31b7d6f649a76751abf6efe2205e7746885ac69af9a17f9 · 181,224 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 19:09 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.