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: 825a29b080fe9014f798628640a26f31797958d398530ea3f701a6882e91ee3c
Tx prefix hash: c2471eb929f86f7b6299dec9b64cbdd0fd2c95dc5afef5bb0b946714d9de09f6
Tx public key: 6f9f0fac5bd36e3b6b3c5515539cdb183d2bd4be4eb80ee3304ff3830b63c8aa
| Timestamp: 1780068218 | Timestamp [UTC]: 2026-05-29 15:23:38 | Age [y:d:h:m:s]: 00:010:09:23:09 |
| Block: 4612 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3274 | RingCT/type: yes/0 |
| Extra: 016f9f0fac5bd36e3b6b3c5515539cdb183d2bd4be4eb80ee3304ff3830b63c8aa02090000000226697be300 | ||
1 output(s) for total of 34.876289568726 HMNY
| stealth address | amount | amount idx | tag |
| 00: 67a4e4bd584904710c8941f6eda909068598d3416e0ec16b4c2bd6d9d4fda30d | 34.876289568726 | 5791 of 0 | <ef> |
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": 4672,
"vin": [ {
"gen": {
"height": 4612
}
}
],
"vout": [ {
"amount": 34876289568726,
"target": {
"tagged_key": {
"key": "67a4e4bd584904710c8941f6eda909068598d3416e0ec16b4c2bd6d9d4fda30d",
"view_tag": "ef"
}
}
}
],
"extra": [ 1, 111, 159, 15, 172, 91, 211, 110, 59, 107, 60, 85, 21, 83, 156, 219, 24, 61, 43, 212, 190, 78, 184, 14, 227, 48, 79, 243, 131, 11, 99, 200, 170, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}