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: 9dd6301fa14bb83cf49984aeb4676d381465fb697995c8c6eb088c1c7d181cd1
Tx prefix hash: fa07de2376c833d6c4201970995c3351b0d13011b1e779457ed0ac411fa302c7
Tx public key: cd32df0ec9d056e7149ecb6c00cad5c55c2a01766746708c934880be6bd00ca9
| Timestamp: 1779537322 | Timestamp [UTC]: 2026-05-23 11:55:22 | Age [y:d:h:m:s]: 00:024:20:40:52 |
| Block: 684 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 8061 | RingCT/type: yes/0 |
| Extra: 01cd32df0ec9d056e7149ecb6c00cad5c55c2a01766746708c934880be6bd00ca902090000001aba6d17be00 | ||
1 output(s) for total of 35.141168133514 HMNY
| stealth address | amount | amount idx | tag |
| 00: a9ea016b60a44d3c3be0d9514e3ec6b580a4aa5927e9ab8d6fdf7a91aa3a7b8f | 35.141168133514 | 765 of 0 | <98> |
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": 744,
"vin": [ {
"gen": {
"height": 684
}
}
],
"vout": [ {
"amount": 35141168133514,
"target": {
"tagged_key": {
"key": "a9ea016b60a44d3c3be0d9514e3ec6b580a4aa5927e9ab8d6fdf7a91aa3a7b8f",
"view_tag": "98"
}
}
}
],
"extra": [ 1, 205, 50, 223, 14, 201, 208, 86, 231, 20, 158, 203, 108, 0, 202, 213, 197, 92, 42, 1, 118, 103, 70, 112, 140, 147, 72, 128, 190, 107, 208, 12, 169, 2, 9, 0, 0, 0, 26, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}