Transaction

What happened, step by step

1. meta to dev-1665612656497-17549308116426

   proxy_call()

   Arguments (140 bytes)

   {
     "contract_id": "dev-1665760167043-23319134756688",
     "method": "register",
     "user_args": "{\"round_id\": 66}",
     "amount": "1000000000000000000000000"
   }

   Logs (4)

   meta tipped 950000000000000000000000 of "NEAR" to NEAR account dev-1665760167043-23319134756688
   EVENT_JSON:{"data":[{"account_id":"dev-1665760167043-23319134756688","amount":"950000000000000000000000","token_id":"NEAR"}],"event":"deposit","standard":"tipbot","version":"1.0.0"}
   EVENT_JSON:{"data":[{"amount":"950000000000000000000000","receiver_near_account":"dev-1665760167043-23319134756688","receiver_service_account":null,"sender_account_id":"meta","token_id":"NEAR"}],"event":"tip","standard":"tipbot","version":"1.0.0"}
   EVENT_JSON:{"data":[{"account_id":"meta","amount":"50000000000000000000000","token_id":"NEAR"}],"event":"treasury_add","standard":"tipbot","version":"1.0.0"}

2. dev-1665612656497-17549308116426 to dev-1665760167043-23319134756688

   register()

   Arguments (81 bytes)

   {
     "amount": "950000000000000000000000",
     "token_id": null,
     "args": "{\"round_id\": 66}"
   }

2 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":"85ZeSjVdgsr1CZXC6q91Snabr4uK2ecpunPg7qvnCury","sender_account_id":"meta","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.