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: 57ede62b7f37cf63a4390a7ec0dee92551f8d0b60c8c8bb44ff6e5d561aa44f0
Tx prefix hash: 348f30fe4ac88b1088b61fd7b434e1973518bc05071ce5658d51124e1be89ccb
Tx public key: a10b7e9c121279fd1edc74e7199aa122cb9e27080e98111cc84aaa9967753a6e
| Timestamp: 1779472602 | Timestamp [UTC]: 2026-05-22 17:56:42 | Age [y:d:h:m:s]: 00:017:23:12:21 |
| Block: 581 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 8154 | RingCT/type: yes/0 |
| Extra: 01a10b7e9c121279fd1edc74e7199aa122cb9e27080e98111cc84aaa9967753a6e02090000000393369e7d00 | ||
1 output(s) for total of 35.145470432409 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3e9a24788917255975bcc96d69ed3d8e5047a35d247be1db7385a85b837a52dc | 35.145470432409 | 593 of 0 | <87> |
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": 641,
"vin": [ {
"gen": {
"height": 581
}
}
],
"vout": [ {
"amount": 35145470432409,
"target": {
"tagged_key": {
"key": "3e9a24788917255975bcc96d69ed3d8e5047a35d247be1db7385a85b837a52dc",
"view_tag": "87"
}
}
}
],
"extra": [ 1, 161, 11, 126, 156, 18, 18, 121, 253, 30, 220, 116, 231, 25, 154, 161, 34, 203, 158, 39, 8, 14, 152, 17, 28, 200, 74, 170, 153, 103, 117, 58, 110, 2, 9, 0, 0, 0, 3, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}