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: 9b409d3b2c24311c219724cb1ae579b86a7b6b159a16dde50f7fa9657d77dfae
Tx prefix hash: 63c6c9d3d107e6b5dfe7a89931dc27a7ad2de850a830989fc3ca67f006850cf2
Tx public key: 53c88cbb99bfd329f766544e41e2aaa1c89c095123f75b2441df2f9e666ad05c
| Timestamp: 1779713967 | Timestamp [UTC]: 2026-05-25 12:59:27 | Age [y:d:h:m:s]: 00:014:11:47:20 |
| Block: 1607 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6279 | RingCT/type: yes/0 |
| Extra: 0153c88cbb99bfd329f766544e41e2aaa1c89c095123f75b2441df2f9e666ad05c020900000001ba6d17be00 | ||
1 output(s) for total of 35.076760053575 HMNY
| stealth address | amount | amount idx | tag |
| 00: 97d829e4c72d9c661a01148933696d51f8b3fb199f865fff0ffeb66effa061c6 | 35.076760053575 | 1765 of 0 | <d5> |
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": 1667,
"vin": [ {
"gen": {
"height": 1607
}
}
],
"vout": [ {
"amount": 35076760053575,
"target": {
"tagged_key": {
"key": "97d829e4c72d9c661a01148933696d51f8b3fb199f865fff0ffeb66effa061c6",
"view_tag": "d5"
}
}
}
],
"extra": [ 1, 83, 200, 140, 187, 153, 191, 211, 41, 247, 102, 84, 78, 65, 226, 170, 161, 200, 156, 9, 81, 35, 247, 91, 36, 65, 223, 47, 158, 102, 106, 208, 92, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}