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: f06c6b676b7ffab840eb1eaff5faccc3b5c56057006d5abf08db0f7fbdb8ee3f
Tx prefix hash: ccc695aa893e2384bb3fbd152bd5743dae374a7271c15849d452fe70c19808ae
Tx public key: 8eaa1fd961d1aac70fc2850b42285c218dec02c603f4be03bbd1edc8851716e6
| Timestamp: 1780689708 | Timestamp [UTC]: 2026-06-05 20:01:48 | Age [y:d:h:m:s]: 00:003:04:44:59 |
| Block: 5614 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2272 | RingCT/type: yes/0 |
| Extra: 018eaa1fd961d1aac70fc2850b42285c218dec02c603f4be03bbd1edc8851716e6020900000001e49593ff00 | ||
1 output(s) for total of 34.809698872624 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9185366405e4ffdc3b73ea198912743b6201e0b24ee11be4bb41717b88500849 | 34.809698872624 | 7061 of 0 | <82> |
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": 5674,
"vin": [ {
"gen": {
"height": 5614
}
}
],
"vout": [ {
"amount": 34809698872624,
"target": {
"tagged_key": {
"key": "9185366405e4ffdc3b73ea198912743b6201e0b24ee11be4bb41717b88500849",
"view_tag": "82"
}
}
}
],
"extra": [ 1, 142, 170, 31, 217, 97, 209, 170, 199, 15, 194, 133, 11, 66, 40, 92, 33, 141, 236, 2, 198, 3, 244, 190, 3, 187, 209, 237, 200, 133, 23, 22, 230, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}