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: d2cde9048c883bf9efcb48002c2d3fcb0eb19d212a0849abedd6c17abd93c968
Tx prefix hash: 3446ae4d4f4aefc83fbcb10c072d97dfedb8cf62a7c13e873667ce2f448cb602
Tx public key: f4a088a25fbd3b79a0d014f52ddf98b371d3de4bc3ed401d13223b843633702a
| Timestamp: 1779640283 | Timestamp [UTC]: 2026-05-24 16:31:23 | Age [y:d:h:m:s]: 00:015:04:40:44 |
| Block: 1286 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6600 | RingCT/type: yes/0 |
| Extra: 01f4a088a25fbd3b79a0d014f52ddf98b371d3de4bc3ed401d13223b843633702a020900000001ba6d17be00 | ||
1 output(s) for total of 35.098242708782 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1ee58e27471a8bfc02c68260dcbe3ef0825f21c23674106af438ebe13d314b04 | 35.098242708782 | 1434 of 0 | <6a> |
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": 1346,
"vin": [ {
"gen": {
"height": 1286
}
}
],
"vout": [ {
"amount": 35098242708782,
"target": {
"tagged_key": {
"key": "1ee58e27471a8bfc02c68260dcbe3ef0825f21c23674106af438ebe13d314b04",
"view_tag": "6a"
}
}
}
],
"extra": [ 1, 244, 160, 136, 162, 95, 189, 59, 121, 160, 208, 20, 245, 45, 223, 152, 179, 113, 211, 222, 75, 195, 237, 64, 29, 19, 34, 59, 132, 54, 51, 112, 42, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}