Transaction

What happened, step by step

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

1. agentbazaar.testnet to wrap.testnet

   ft_transfer_call() with 1 yoctoNEAR

   Arguments (250 bytes)

   {
     "receiver_id": "ref-finance.testnet",
     "amount": "40000000000000000000000",
     "msg": "{\"actions\":[{\"pool_id\":11,\"token_in\":\"wrap.testnet\",\"token_out\":\"banana.ft-fin.testnet\",\"amount_in\":\"40000000000000000000000\",\"min_amount_out\":\"1\"}]}"
   }

   Logs (1)

   Transfer 40000000000000000000000 from agentbazaar.testnet to ref-finance.testnet

2. wrap.testnet to ref-finance.testnet · failed

   ft_on_transfer()

   Arguments (248 bytes)

   {
     "sender_id": "agentbazaar.testnet",
     "amount": "40000000000000000000000",
     "msg": "{\"actions\":[{\"pool_id\":11,\"token_in\":\"wrap.testnet\",\"token_out\":\"banana.ft-fin.testnet\",\"amount_in\":\"40000000000000000000000\",\"min_amount_out\":\"1\"}]}"
   }

   Smart contract panicked: panicked at 'ERR_MSG_WRONG_FORMAT: Error("data did not match any variant of untagged enum TokenReceiverMessage", line: 0, column: 0)', ref-exchange/src/token_receiver.rs:90:68

3. wrap.testnet to wrap.testnet

   ft_resolve_transfer()

   Arguments (106 bytes)

   {
     "sender_id": "agentbazaar.testnet",
     "receiver_id": "ref-finance.testnet",
     "amount": "40000000000000000000000"
   }

   Logs (1)

   Refund 40000000000000000000000 from ref-finance.testnet to agentbazaar.testnet

3 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":"DBKCHuoCzvySFMt5VG6jyUveZNPLqQj4M1RHtdFRud4u","sender_account_id":"agentbazaar.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.