TRENCH
The creator took 48% of supply at 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.
noteThe creator took 48.3% of supply at launch.
At launch
| Created | 2026-09-29 20:09 UTC |
| Creator | 4Zo7GdWmbxAuzYuUjirvFwd6Fk61x1V7Ck3Zz9Tybu7W |
| Creator took | 48.3% of supply in the first block |
| Outside buyers | 702 distinct wallets, not counting the creator, bought on the bonding curve: 12 within the first 30s, 3 bundled into the creation block. |
| Graduated | 2.7 h 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 | NVynQrcic6HMhty3VBUhpq… slot 451,745,077
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 20:09:44 UTC Slot 451,745,077, which is the chain's own clock for this moment. |
| Creation block | 3 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 12 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. |
| Curve completed | 2026-09-29 22:48:55 UTC +2h 39m 11s Confirmed: a PumpSwap pool was found for it. |
| Highest price seen | 2026-09-29 22:48:55 UTC +2h 39m 11s
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. |
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 166 launches from 132 creator wallets, including this one. See them → |
Pool
| Liquidity | 76.6 SOL |
| Read from chain | 2026-10-01 11:56 UTC, just now |
What this launch claimed to be
| Name | Trench Town |
| Description | Trench Town is an idle RPG where you can battle, farm, earn and gamble. |
| Metadata held | sha256 4a1667455cac80a908467cce3c7b2f1974cde833ea1da4b7af7bc7488e152a2a · 339 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 20:10 UTC. |
| Picture held | sha256 793fee2eb14f664b1a3822dd971e1d21d07f995d494a043cf94d1b592de3715a · 160,530 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 20:09 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.