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: 4c7474882bbe34454230f9e3ce3e53a41c83eeff5b80568cd06803d6cc50fc25
Tx prefix hash: ebfd68a19d4aa15e80dc0a7bc3c82f3a6ecaa05148c11ef18bf4c14758ce0fa7
Tx public key: 2709b557707727391ed1e619aa501294fe5616a5c4e196a31383bf7fa5d1ba6e
| Timestamp: 1779950420 | Timestamp [UTC]: 2026-05-28 06:40:20 | Age [y:d:h:m:s]: 00:011:16:38:33 |
| Block: 3615 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4271 | RingCT/type: yes/0 |
| Extra: 012709b557707727391ed1e619aa501294fe5616a5c4e196a31383bf7fa5d1ba6e02090000000326697be300 | ||
1 output(s) for total of 34.942674411118 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0041a59368e3d699f0bcb31ee4fb1106d9e29cc26ad1b0493d5a5172573d113d | 34.942674411118 | 4366 of 0 | <20> |
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": 3675,
"vin": [ {
"gen": {
"height": 3615
}
}
],
"vout": [ {
"amount": 34942674411118,
"target": {
"tagged_key": {
"key": "0041a59368e3d699f0bcb31ee4fb1106d9e29cc26ad1b0493d5a5172573d113d",
"view_tag": "20"
}
}
}
],
"extra": [ 1, 39, 9, 181, 87, 112, 119, 39, 57, 30, 209, 230, 25, 170, 80, 18, 148, 254, 86, 22, 165, 196, 225, 150, 163, 19, 131, 191, 127, 165, 209, 186, 110, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}