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: 60fcb3d13d1d0d9a5bf8ea85fccf9e13e241724e39400eef0af71bc62d10b94d
Tx prefix hash: fdf10ffec38348cafd1f41e797f7735fbbaa93696bae88f41b534831074e598b
Tx public key: 08f60aa4a046b5d9220c8d595a7e6074a245c9d4ad4a43a9dd8160e5d9c68879
| Timestamp: 1779721355 | Timestamp [UTC]: 2026-05-25 15:02:35 | Age [y:d:h:m:s]: 00:020:21:37:34 |
| Block: 1760 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6985 | RingCT/type: yes/0 |
| Extra: 0108f60aa4a046b5d9220c8d595a7e6074a245c9d4ad4a43a9dd8160e5d9c68879020900000001ba6d17be00 | ||
1 output(s) for total of 35.066525284884 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8ec152cf560019b8c6b6c4fac03eb0f3a06053d3110c958c696ff65fc36e0d63 | 35.066525284884 | 1943 of 0 | <f6> |
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": 1820,
"vin": [ {
"gen": {
"height": 1760
}
}
],
"vout": [ {
"amount": 35066525284884,
"target": {
"tagged_key": {
"key": "8ec152cf560019b8c6b6c4fac03eb0f3a06053d3110c958c696ff65fc36e0d63",
"view_tag": "f6"
}
}
}
],
"extra": [ 1, 8, 246, 10, 164, 160, 70, 181, 217, 34, 12, 141, 89, 90, 126, 96, 116, 162, 69, 201, 212, 173, 74, 67, 169, 221, 129, 96, 229, 217, 198, 136, 121, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}