For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: ed498dfb7d1663cb28b7b7007b5e1b0420dc5fe9908d5d08df1c284c3579084f
Tx prefix hash: d3041a209fc99b1521c7da5f148751d3513ab836a7d9d92af5564e037623aaa2
Tx public key: 5197e692a3b1501ccf3d70a5f8debd264db484ae3e63a9327748c9ddfe6f862a
| Timestamp: 1780130001 | Timestamp [UTC]: 2026-05-30 08:33:21 | Age [y:d:h:m:s]: 00:014:02:28:55 |
| Block: 4932 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3813 | RingCT/type: yes/0 |
| Extra: 015197e692a3b1501ccf3d70a5f8debd264db484ae3e63a9327748c9ddfe6f862a02090000000226697be300 | ||
1 output(s) for total of 34.855009245499 HMNY
| stealth address | amount | amount idx | tag |
| 00: bf5861ced5a7359639fdb37468da8e9ccbb33d4b0d0b143dc8c4421c8238f70f | 34.855009245499 | 6263 of 0 | <d2> |
Check which outputs belong to given HMNY address/subaddress and viewkey
For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side
Prove to someone that you have sent them HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side
{
"version": 2,
"unlock_time": 4992,
"vin": [ {
"gen": {
"height": 4932
}
}
],
"vout": [ {
"amount": 34855009245499,
"target": {
"tagged_key": {
"key": "bf5861ced5a7359639fdb37468da8e9ccbb33d4b0d0b143dc8c4421c8238f70f",
"view_tag": "d2"
}
}
}
],
"extra": [ 1, 81, 151, 230, 146, 163, 177, 80, 28, 207, 61, 112, 165, 248, 222, 189, 38, 77, 180, 132, 174, 62, 99, 169, 50, 119, 72, 201, 221, 254, 111, 134, 42, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}