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: 16b942423844944aa8faee356f86a61821136bbb5bb4bee772c7eae20819b86c
Tx prefix hash: 8b7cf4ad11c966630f4a42d9a345cc9d21750045e675a03b1d86250ee30cd828
Tx public key: f252f2c671d65356f3e295bcdff4ede8c61955e82613ad033dadf22382f67241
| Timestamp: 1781013644 | Timestamp [UTC]: 2026-06-09 14:00:44 | Age [y:d:h:m:s]: 00:006:03:15:41 |
| Block: 8610 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 135 | RingCT/type: yes/0 |
| Extra: 01f252f2c671d65356f3e295bcdff4ede8c61955e82613ad033dadf22382f67241020900000004e49593ff00 | ||
1 output(s) for total of 34.616372032853 HMNY
| stealth address | amount | amount idx | tag |
| 00: 96d38add74d5aae617ce7d05a47eb2e3350698a2e0c0457922df5e5ac9f7eb9f | 34.616372032853 | 10640 of 0 | <9c> |
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": 8670,
"vin": [ {
"gen": {
"height": 8610
}
}
],
"vout": [ {
"amount": 34616372032853,
"target": {
"tagged_key": {
"key": "96d38add74d5aae617ce7d05a47eb2e3350698a2e0c0457922df5e5ac9f7eb9f",
"view_tag": "9c"
}
}
}
],
"extra": [ 1, 242, 82, 242, 198, 113, 214, 83, 86, 243, 226, 149, 188, 223, 244, 237, 232, 198, 25, 85, 232, 38, 19, 173, 3, 61, 173, 242, 35, 130, 246, 114, 65, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}