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: 33ee6b9a129559fb6e3d2bafe20f22e238e56a318de0d274b02d71e64a01f0a2
Tx prefix hash: e9bbd13978954f699b2e8290b5f0163411dcd6aa2cfe92f5b81e6e6dffb82536
Tx public key: 01683698f48fc3e872d0ccc03c9adfdfc30fd6a445b83123b5fd4542df56858b
| Timestamp: 1780051673 | Timestamp [UTC]: 2026-05-29 10:47:53 | Age [y:d:h:m:s]: 00:010:15:52:43 |
| Block: 4407 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3490 | RingCT/type: yes/0 |
| Extra: 0101683698f48fc3e872d0ccc03c9adfdfc30fd6a445b83123b5fd4542df56858b02090000000526697be300 | ||
1 output(s) for total of 34.889929102995 HMNY
| stealth address | amount | amount idx | tag |
| 00: e7808600b676705adb0bc7c706634a6676c3501edafd15907b8d903e54ee006b | 34.889929102995 | 5512 of 0 | <c1> |
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": 4467,
"vin": [ {
"gen": {
"height": 4407
}
}
],
"vout": [ {
"amount": 34889929102995,
"target": {
"tagged_key": {
"key": "e7808600b676705adb0bc7c706634a6676c3501edafd15907b8d903e54ee006b",
"view_tag": "c1"
}
}
}
],
"extra": [ 1, 1, 104, 54, 152, 244, 143, 195, 232, 114, 208, 204, 192, 60, 154, 223, 223, 195, 15, 214, 164, 69, 184, 49, 35, 181, 253, 69, 66, 223, 86, 133, 139, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}