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: fa4fc32e260fc1c3c9419b9a015298a1fa8c3383fd29fe8d2a79d3f4e0455914
Tx prefix hash: 9be671b07df8b01958a7f256fee7111b1fb46cf78b6a1bdc857e7330052cae4e
Tx public key: 8ae1d4f64e580321eae6654d2e1462434fc0fbfeefca5bb893247758c2d2e451
| Timestamp: 1780797615 | Timestamp [UTC]: 2026-06-07 02:00:15 | Age [y:d:h:m:s]: 00:006:09:02:01 |
| Block: 6781 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1964 | RingCT/type: yes/0 |
| Extra: 018ae1d4f64e580321eae6654d2e1462434fc0fbfeefca5bb893247758c2d2e451020900000001e49593ff00 | ||
1 output(s) for total of 34.735726499460 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3bde40650b1b9f791470eb3d28f48036a81ae4bf1a89f9935ae6010d39fd3879 | 34.735726499460 | 8373 of 0 | <86> |
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": 6841,
"vin": [ {
"gen": {
"height": 6781
}
}
],
"vout": [ {
"amount": 34735726499460,
"target": {
"tagged_key": {
"key": "3bde40650b1b9f791470eb3d28f48036a81ae4bf1a89f9935ae6010d39fd3879",
"view_tag": "86"
}
}
}
],
"extra": [ 1, 138, 225, 212, 246, 78, 88, 3, 33, 234, 230, 101, 77, 46, 20, 98, 67, 79, 192, 251, 254, 239, 202, 91, 184, 147, 36, 119, 88, 194, 210, 228, 81, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}