TRENCH
The curve completed 6s 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.
noteThe creator took 30.4% of supply at launch.
findingIt left the curve 6s after launch.
noteOnly 4.3 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-09-29 17:30 UTC |
| Creator | AV7PjXHL5JXZ1YoYRoN9Dsstg1x2UciBupMCXcJP8gUz |
| Creator took | 30.4% of supply in the first block |
| Outside buyers | 32 distinct wallets, not counting the creator, bought on the bonding curve: 32 within the first 30s, 5 bundled into the creation block. |
| Graduated | 0 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 1.3 days ago and it was finished. Checked 2026-09-29 17:32 UTC. |
| Creator sold | not while we watched |
| Recorded from | 4APMvXu6MoG8mJ7F8BG5KL… slot 451,709,420
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 17:30:35 UTC Slot 451,709,420, which is the chain's own clock for this moment. |
| Creation block | 5 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Curve completed | 2026-09-29 17:30:41 UTC +6s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-09-29 17:30:41 UTC +6s
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 | 32 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 40 launches from 18 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 165 launches from 131 creator wallets, including this one. See them → |
| This creator | 1,398 earlier launches, 52 confirmed graduated on chain, 6 with findings on record. See the creator's launches → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 644 other creator wallets, across 1,095 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 | 4.3 SOL |
| Read from chain | 2026-09-30 23:39 UTC, just now |
What this launch claimed to be
| Name | trench.io |
| Description | Fees to @trytrenchio via UsePaid |
| Metadata held | sha256 344bfb57fb7ce8216b7f30c3a524d502bab40dd5c81cc06551ab474bf60bcae5 · 265 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 17:32 UTC. |
| Picture held | sha256 a2b44865a2014a4ee569c2944125db05dd9f2b5e55c5d479a5ac75ec74ef5e78 · 2,794 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-09-29 17:30 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.