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: db6f032f347e3584abc5c991888c0e0df85286022c7161fe86b4628343aae403
Tx prefix hash: a1e6f0044cf8da833f5b7d3fa7f00b47655e9592d62d4eae0af94f50ca33c4e3
Tx public key: 90ae81bc790f0a6ab594c2a8067ae9b9c93a09dbe3a9f7f98f3d95d9b3a98372
| Timestamp: 1780985794 | Timestamp [UTC]: 2026-06-09 06:16:34 | Age [y:d:h:m:s]: 00:000:07:21:02 |
| Block: 8139 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 459 | RingCT/type: yes/0 |
| Extra: 0190ae81bc790f0a6ab594c2a8067ae9b9c93a09dbe3a9f7f98f3d95d9b3a98372020900000001e49593ff00 | ||
1 output(s) for total of 34.642456326390 HMNY
| stealth address | amount | amount idx | tag |
| 00: afe63d51e5f599f9c60edc022085f273cb1c67867f1a002867fd2ea46de25f1d | 34.642456326390 | 10079 of 0 | <b6> |
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": 8199,
"vin": [ {
"gen": {
"height": 8139
}
}
],
"vout": [ {
"amount": 34642456326390,
"target": {
"tagged_key": {
"key": "afe63d51e5f599f9c60edc022085f273cb1c67867f1a002867fd2ea46de25f1d",
"view_tag": "b6"
}
}
}
],
"extra": [ 1, 144, 174, 129, 188, 121, 15, 10, 106, 181, 148, 194, 168, 6, 122, 233, 185, 201, 58, 9, 219, 227, 169, 247, 249, 143, 61, 149, 217, 179, 169, 131, 114, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}