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: ab98c113df49db91100b3d120d44e3af07aa7c549a2b0b1603bd7005a0481b66
Tx prefix hash: a89d2286b33774b0fdc0acf25176e527e16179e2aeaea916b0c37706cbf5d0f9
Tx public key: b87eccd64d3cb4b66a5ccd1e262b26bc4fce367e00e9a5eb5152a2c4e851b609
| Timestamp: 1779917641 | Timestamp [UTC]: 2026-05-27 21:34:01 | Age [y:d:h:m:s]: 00:012:03:12:46 |
| Block: 3329 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4557 | RingCT/type: yes/0 |
| Extra: 01b87eccd64d3cb4b66a5ccd1e262b26bc4fce367e00e9a5eb5152a2c4e851b60902090000000326697be300 | ||
1 output(s) for total of 34.961740917842 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1b28e26706b3488ab2fa987b8ccbc07a05da7eb9c8a3f46c2d6f1c7a9c8954e5 | 34.961740917842 | 3999 of 0 | <c6> |
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": 3389,
"vin": [ {
"gen": {
"height": 3329
}
}
],
"vout": [ {
"amount": 34961740917842,
"target": {
"tagged_key": {
"key": "1b28e26706b3488ab2fa987b8ccbc07a05da7eb9c8a3f46c2d6f1c7a9c8954e5",
"view_tag": "c6"
}
}
}
],
"extra": [ 1, 184, 126, 204, 214, 77, 60, 180, 182, 106, 92, 205, 30, 38, 43, 38, 188, 79, 206, 54, 126, 0, 233, 165, 235, 81, 82, 162, 196, 232, 81, 182, 9, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}