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: 23dcc8176a5e9b600ba052890e8ccc86add9fabfaffb536e7e088305f0f2cffc
Tx prefix hash: 471d51b16cdb9c5f1298773d2fdb71716b9f0f6034e9ce133aec63cf8d8cc169
Tx public key: a9e5c2fef98113d103201f4b0b56847c14a323779abf6fb592f0f5b800d033ec
| Timestamp: 1779714646 | Timestamp [UTC]: 2026-05-25 13:10:46 | Age [y:d:h:m:s]: 00:018:21:51:30 |
| Block: 1621 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7124 | RingCT/type: yes/0 |
| Extra: 01a9e5c2fef98113d103201f4b0b56847c14a323779abf6fb592f0f5b800d033ec020900000001ba6d17be00 | ||
1 output(s) for total of 35.075823414643 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6a98f747819f8701c6171a26d3079bff65fd872c6d437e4009cefd53256d2918 | 35.075823414643 | 1779 of 0 | <4c> |
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": 1681,
"vin": [ {
"gen": {
"height": 1621
}
}
],
"vout": [ {
"amount": 35075823414643,
"target": {
"tagged_key": {
"key": "6a98f747819f8701c6171a26d3079bff65fd872c6d437e4009cefd53256d2918",
"view_tag": "4c"
}
}
}
],
"extra": [ 1, 169, 229, 194, 254, 249, 129, 19, 209, 3, 32, 31, 75, 11, 86, 132, 124, 20, 163, 35, 119, 154, 191, 111, 181, 146, 240, 245, 184, 0, 208, 51, 236, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}