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: 9c0591b42110eabf51c28c27a0e9dcc51a56878d3a52fafdac07648272d5f3b6
Tx prefix hash: d3041fccaab523ee7ce6c0e39676df8be536bb9f0ea3dcb26304ceebea43fc2a
Tx public key: f7c9dd872a2c8025a3475695afdcc65fd5df84943abbf4d48e8245e86a50419b
| Timestamp: 1779733877 | Timestamp [UTC]: 2026-05-25 18:31:17 | Age [y:d:h:m:s]: 00:014:07:04:40 |
| Block: 1899 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5987 | RingCT/type: yes/0 |
| Extra: 01f7c9dd872a2c8025a3475695afdcc65fd5df84943abbf4d48e8245e86a50419b02090000000326697be300 | ||
1 output(s) for total of 35.059839619934 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9cf07ee1cd15f2b7e44f9a7ffa6bfefb9ea132666fbd899740d9a3ac39051ed4 | 35.059839619934 | 2125 of 0 | <e0> |
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": 1959,
"vin": [ {
"gen": {
"height": 1899
}
}
],
"vout": [ {
"amount": 35059839619934,
"target": {
"tagged_key": {
"key": "9cf07ee1cd15f2b7e44f9a7ffa6bfefb9ea132666fbd899740d9a3ac39051ed4",
"view_tag": "e0"
}
}
}
],
"extra": [ 1, 247, 201, 221, 135, 42, 44, 128, 37, 163, 71, 86, 149, 175, 220, 198, 95, 213, 223, 132, 148, 58, 187, 244, 212, 142, 130, 69, 232, 106, 80, 65, 155, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}