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: 7dc6e9bd5b3e406d4cb8f000fc1f64f517762dd06f11322b02286acd76a5ea1d
Tx prefix hash: b9e6410a6b3b4a853f034710fc3311bb026b81df1cb23f8ca938071762591bd3
Tx public key: e2ec5d61965a8100963fb24af7363150b3b13dc6d058434f571ea80280544821
| Timestamp: 1780055966 | Timestamp [UTC]: 2026-05-29 11:59:26 | Age [y:d:h:m:s]: 00:010:13:36:31 |
| Block: 4456 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3430 | RingCT/type: yes/0 |
| Extra: 01e2ec5d61965a8100963fb24af7363150b3b13dc6d058434f571ea8028054482102090000000326697be300 | ||
1 output(s) for total of 34.886668436588 HMNY
| stealth address | amount | amount idx | tag |
| 00: 083654538bd46c8a32f328afb0bbf0d92d4cb0671c621aadce2861ce03e78363 | 34.886668436588 | 5579 of 0 | <f3> |
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": 4516,
"vin": [ {
"gen": {
"height": 4456
}
}
],
"vout": [ {
"amount": 34886668436588,
"target": {
"tagged_key": {
"key": "083654538bd46c8a32f328afb0bbf0d92d4cb0671c621aadce2861ce03e78363",
"view_tag": "f3"
}
}
}
],
"extra": [ 1, 226, 236, 93, 97, 150, 90, 129, 0, 150, 63, 178, 74, 247, 54, 49, 80, 179, 177, 61, 198, 208, 88, 67, 79, 87, 30, 168, 2, 128, 84, 72, 33, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}