PACT
Checked at birth, no markers found; pool below threshold when last readWe watched this launch and checked it against every marker we record; none is present. Separately, the pool balance was below our threshold when it was last read - a present-tense measurement with its own age, stated below, and not part of the launch record.
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.
noteOnly 1.4 SOL of liquidity was in the pool just now.
At launch
| Created | 2026-10-02 15:48 UTC |
| Creator | EfmF6asZubSLk2V23bTfqQh62Yuym7SbektfcSiRqaDJ |
| Creator took | 3.3% of supply in the first block |
| Outside buyers | 1,001 distinct wallets, not counting the creator, bought on the bonding curve: 184 within the first 30s, 21 bundled into the creation block. |
| Graduated | 6 min after launch |
| Curve, read on chain | Complete. We read the bonding curve account 3.6 h ago and it was finished. Checked 2026-10-02 16:31 UTC. |
| Creator sold | not while we watched |
| Recorded from | ioTdJ7uF58cfNNkddV4fC3… slot 452,655,278
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 15:48:57 UTC Slot 452,655,278, which is the chain's own clock for this moment. |
| Creation block | 21 wallets bought in the block the token was created in, before anyone outside could have seen it exist. |
| Thirty seconds in | 184 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-10-02 15:54:34 UTC +5m 37s Confirmed against the venue's own completion state. |
| Highest price seen | 2026-10-02 15:54:34 UTC +5m 37s
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 | On 5 launches from 5 creator wallets, including this one. Identical bytes, matched by sha256: not a similar image, the same one. See them → |
| This ticker | On 29 launches from 27 creator wallets, including this one. See them → |
| Birth artifacts | Launches by this creator share byte-identical artifacts with launches from 4 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 | 1.4 SOL |
| Read from chain | 2026-10-02 20:08 UTC, just now |
What this launch claimed to be
| Name | Tradepact |
| Metadata held | sha256 0cc95767d9a39d399fa67f8ff7daab4da0c7e5b48a1067b8b4370da3e2e0b2f3 · 288 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 1d61c4f8b244db1a8ac49bee7ea98987c1a735b5127f3d2f3506259357015a9c · 40,680 bytes |
Off-chain and mutable. This is what the launch served when we read it at 2026-10-02 15:48 UTC; the creator can change or unpin any of it at any time, and a launch record is the only place it survives.