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: f330e81fdb6d395d4e56aad8f5d1863bfc9ec7847aa4f17d19b09ef8a5a3fc68
Tx prefix hash: 56383201fb80a6cdbe3832e70f8a7cdb7dc2ac25c0d045d30caca0f1b3aaaa53
Tx public key: 7bd99888c917750e9af882b7f12fcb36d4fcc560c547dabfff4c2c27a4b992ce
| Timestamp: 1779633431 | Timestamp [UTC]: 2026-05-24 14:37:11 | Age [y:d:h:m:s]: 00:016:02:31:52 |
| Block: 986 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7748 | RingCT/type: yes/0 |
| Extra: 017bd99888c917750e9af882b7f12fcb36d4fcc560c547dabfff4c2c27a4b992ce020900000001ba6d17be00 | ||
1 output(s) for total of 35.118331850515 HMNY
| stealth address | amount | amount idx | tag |
| 00: 64998ccff6d03f64e6ce8d5161060b19d1dc7249a59484cf65d8f1b97d509e44 | 35.118331850515 | 1122 of 0 | <81> |
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": 1046,
"vin": [ {
"gen": {
"height": 986
}
}
],
"vout": [ {
"amount": 35118331850515,
"target": {
"tagged_key": {
"key": "64998ccff6d03f64e6ce8d5161060b19d1dc7249a59484cf65d8f1b97d509e44",
"view_tag": "81"
}
}
}
],
"extra": [ 1, 123, 217, 152, 136, 201, 23, 117, 14, 154, 248, 130, 183, 241, 47, 203, 54, 212, 252, 197, 96, 197, 71, 218, 191, 255, 76, 44, 39, 164, 185, 146, 206, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}