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: 49272824aceeb74042b9e3c16a89a421b85343a6988f0925f30bba080db764a2
Tx prefix hash: 62dc5cb6112977235f1038e1fa20d28da943a471674d96b9a71ad4a3401b3711
Tx public key: af563d10b3573bd61123e3dfc12b906f739940b2ac89b6cd84b9941a295c17db
| Timestamp: 1780695585 | Timestamp [UTC]: 2026-06-05 21:39:45 | Age [y:d:h:m:s]: 00:003:03:56:12 |
| Block: 5978 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1908 | RingCT/type: yes/0 |
| Extra: 01af563d10b3573bd61123e3dfc12b906f739940b2ac89b6cd84b9941a295c17db020900000001e49593ff00 | ||
1 output(s) for total of 34.785539736810 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3e492d840ef62728aafff32894aa51a2b10c8391e6a68560ad0a2bfc3e665bb3 | 34.785539736810 | 7443 of 0 | <61> |
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": 6038,
"vin": [ {
"gen": {
"height": 5978
}
}
],
"vout": [ {
"amount": 34785539736810,
"target": {
"tagged_key": {
"key": "3e492d840ef62728aafff32894aa51a2b10c8391e6a68560ad0a2bfc3e665bb3",
"view_tag": "61"
}
}
}
],
"extra": [ 1, 175, 86, 61, 16, 179, 87, 59, 214, 17, 35, 227, 223, 193, 43, 144, 111, 115, 153, 64, 178, 172, 137, 182, 205, 132, 185, 148, 26, 41, 92, 23, 219, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}