NEAR Intents, resolved
A receipt for money that crossed chains.
Paste a transaction hash, a deposit address or your wallet. Get back what actually happened to the swap, with both ends proven on their own chains.
Reads across
Case 42664
The case it was built on was wrong.
A $193,000 deposit, reported publicly as lost. One hash resolved it.
11 Sep
575,830 TRX lands
Credited to intents.near
NEAR chain
27 Sep
190,995.29 USDT delivered
Reached the quoted recipient
Ethereum, block 26,068,435
- !
9 Oct
Reported as lost
Twelve days after it arrived. Still unanswered.
Forum thread 42664
The poster cited a refund field reading zero as proof of loss. On a settled swap, zero is the correct value.
Not a broken system. An unanswerable one.
965 of the last 1,000 swaps settled, measured 28 October. The problem is the tail nobody can see into.
swaps took a deposit and went nowhere
of quoted notional sitting in them
days, the median age. The oldest waited 292.
Measured 26 Oct 2026 against the Intents Explorer. Counts only, no addresses.
The receipt
One hash in. The proof out.
Every line is read from a public chain, and delivery is proven against the destination chain itself, not taken from the operator.
- deposit
- TBy2io3Q3Jt4UM4ejDhkkUQJZgZuXw2sus
- status
- SUCCESS · last changed 27 Sep 2026
- credited
- 575,830 TRX to intents.near
- destination
- 0x9be9c2f8…e13421a on Ethereum
- proven
- 190,995.293894 USDT · block 26,068,435
Eight answers. Never a guess.
Each verdict carries its evidence, its next step, and the edge of what it can see.
Delivered
Refunded
In flight
Stranded
Wrong door
Locked out
Shielded
Undetermined
The id you hold cannot be looked up.
Three reads of one swap, three different ids. It traces a request, not the money.