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: 73613bd08d00ea8a2eef5d3321290da3f921b08c6c9c55095c2202c66a99f73a
Tx prefix hash: a9a68fc28e54863bf72f49cc7cbc20d407e20d500ebbed0ff435c91077b7e54d
Tx public key: 6e8f2f49acca6c8b9328a3d584bfd63bf19800f4e7f39fb054fb4a30f79b22b9
| Timestamp: 1779635339 | Timestamp [UTC]: 2026-05-24 15:08:59 | Age [y:d:h:m:s]: 00:015:10:26:58 |
| Block: 1077 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6809 | RingCT/type: yes/0 |
| Extra: 016e8f2f49acca6c8b9328a3d584bfd63bf19800f4e7f39fb054fb4a30f79b22b9020900000001ba6d17be00 | ||
1 output(s) for total of 35.112236929558 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4c55de4e2a9c8c3756dd7ad9335ebb26a93c09ce683deebd834ab0cf17ad262c | 35.112236929558 | 1215 of 0 | <24> |
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": 1137,
"vin": [ {
"gen": {
"height": 1077
}
}
],
"vout": [ {
"amount": 35112236929558,
"target": {
"tagged_key": {
"key": "4c55de4e2a9c8c3756dd7ad9335ebb26a93c09ce683deebd834ab0cf17ad262c",
"view_tag": "24"
}
}
}
],
"extra": [ 1, 110, 143, 47, 73, 172, 202, 108, 139, 147, 40, 163, 213, 132, 191, 214, 59, 241, 152, 0, 244, 231, 243, 159, 176, 84, 251, 74, 48, 247, 155, 34, 185, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}