Transaction

What happened, step by step

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

1. nlqms07287488b.testnet to nlqms07287488.sputnikv2.testnet

   act_proposal()

   Arguments (193 bytes)

   {
     "id": 36,
     "action": "VoteApprove",
     "proposal": {
       "UpgradeRemote": {
         "receiver_id": "fmwgalq49.ainearb6872.testnet",
         "method_name": "apply_upgrade",
         "hash": "3KQGx1pFFLfZbhY5DiGY5Lf4XMh9cogzpDcqMN2HgPz4"
       }
     }
   }

2. nlqms07287488.sputnikv2.testnet to nlqms07287488a.testnet

   Transfer with 1.0000 NEAR

3. nlqms07287488.sputnikv2.testnet to fmwgalq49.ainearb6872.testnet · failed

   apply_upgrade()

   Arguments are 614255 bytes, too long to show here. The command below returns them.

   Smart contract panicked: no pending upgrade

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":"CyvHnhBWfF66VDs66vnSzDKxp6PuPiZngDPQQgNgafc1","sender_account_id":"nlqms07287488b.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.