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: 5f5ddf9c3d28910a8e18fd24e91d4dfbdf2e93f291586b4d4292825965dc2aed
Tx prefix hash: dd6a2413f80206a561e18aeff851c328aa912a0c81131d920b07e1cecc203720
Tx public key: e9158fdb98901c71388b7145ca99f9b5c10f9dbc879319c9c9c161001e254840
| Timestamp: 1779881565 | Timestamp [UTC]: 2026-05-27 11:32:45 | Age [y:d:h:m:s]: 00:020:21:03:29 |
| Block: 2948 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5797 | RingCT/type: yes/0 |
| Extra: 01e9158fdb98901c71388b7145ca99f9b5c10f9dbc879319c9c9c161001e25484002090000000226697be300 | ||
1 output(s) for total of 34.987156866995 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5b42b67966335def6a48a51739c35886f7615dc08d78c3dca3dccb39ac84dec6 | 34.987156866995 | 3498 of 0 | <41> |
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": 3008,
"vin": [ {
"gen": {
"height": 2948
}
}
],
"vout": [ {
"amount": 34987156866995,
"target": {
"tagged_key": {
"key": "5b42b67966335def6a48a51739c35886f7615dc08d78c3dca3dccb39ac84dec6",
"view_tag": "41"
}
}
}
],
"extra": [ 1, 233, 21, 143, 219, 152, 144, 28, 113, 56, 139, 113, 69, 202, 153, 249, 181, 193, 15, 157, 188, 135, 147, 25, 201, 201, 193, 97, 0, 30, 37, 72, 64, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}