Transaction

What happened, step by step

A step failed but the transaction finished. Contracts can catch a failed step and carry on.

1. yanganto.testnet to near-swap.yanganto.testnet

   confirm()

   Arguments (383 bytes)

   {
     "sender": "antoyang.testnet",
     "receiver": "yanganto.testnet",
     "amount": 1000000000000000000,
     "hashlock": [
       165,
       152,
       132,
       76,
       216,
       153,
       182,
       114,
       45,
       89,
       20,
       251,
       170,
       95,
       204,
       77,
       214,
       166,
       43,
       58,
       171,
       243,
       206,
       181,
       109,
       46,
       63,
       177,
       197,
       13,
       234,
       154
     ],
     "timelock": 1661491615,
     "secret_key": [
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115,
       115
     ]
   }

   Logs (1)

   confirm with antoyang.testnet

2. near-swap.yanganto.testnet to yanganto.testnet

   Transfer with 1000000000000000000 yoctoNEAR

3. near-swap.yanganto.testnet to platform.near · failed

   Transfer with 1 yoctoNEAR

   {"ActionError":{"index":0,"kind":{"AccountDoesNotExist":{"account_id":"platform.near"}}}}

4 automatic refund steps from the network not shown.

Check this yourself

This page reads FastNEAR's public transaction index and stores nothing. This command asks a NEAR archival node for the same transaction and needs no keys.

curl -s https://archival-rpc.testnet.fastnear.com -H 'Content-Type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"tx","params":{"tx_hash":"8fjmSdBKmdcYmFJZupgJMWCb5x3EzLBbDPoLExD6aJeJ","sender_account_id":"yanganto.testnet","wait_until":"FINAL"}}'

Vouch has its own page because testnet.nearblocks.io stopped indexing on 27 Sep 2026, so it can't show newer transactions.