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: 546213927213b5fef034d1ad22b759297402853472dde3e7fabf9cb3a43bb6de
Tx prefix hash: df81889d8a5df933552100935aa33acde0e84f0605ec8d20cc9e591ae3bb3dc4
Tx public key: 5b4e3ff98be5178e0b144f08a6a5fdf34261a9d82c266e7d3dc3a8a40abd8a7b
| Timestamp: 1780086136 | Timestamp [UTC]: 2026-05-29 20:22:16 | Age [y:d:h:m:s]: 00:010:06:27:32 |
| Block: 4814 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3106 | RingCT/type: yes/0 |
| Extra: 015b4e3ff98be5178e0b144f08a6a5fdf34261a9d82c266e7d3dc3a8a40abd8a7b02090000000726697be300 | ||
1 output(s) for total of 34.862854853042 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5a22a0c7828ecc144430955ec1264afb035893bf198c7023a11bb608e5032a0d | 34.862854853042 | 6056 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": 4874,
"vin": [ {
"gen": {
"height": 4814
}
}
],
"vout": [ {
"amount": 34862854853042,
"target": {
"tagged_key": {
"key": "5a22a0c7828ecc144430955ec1264afb035893bf198c7023a11bb608e5032a0d",
"view_tag": "c6"
}
}
}
],
"extra": [ 1, 91, 78, 63, 249, 139, 229, 23, 142, 11, 20, 79, 8, 166, 165, 253, 243, 66, 97, 169, 216, 44, 38, 110, 125, 61, 195, 168, 164, 10, 189, 138, 123, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}