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: 3e3b9900494e246a5ef05f47518c132889be6d6c8ff9e12b3ef2f9b71275ec01
Tx prefix hash: 2b1f0ad059503d4d54f34a3d6bdc5ea8e54d1e0d3659a2b04e33c0858d6acf56
Tx public key: afb3cb80e26bb9dd17c00174c38028e5f1ba26e819e05ac8a3650759334a6d68
| Timestamp: 1779641605 | Timestamp [UTC]: 2026-05-24 16:53:25 | Age [y:d:h:m:s]: 00:015:10:45:25 |
| Block: 1347 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6599 | RingCT/type: yes/0 |
| Extra: 01afb3cb80e26bb9dd17c00174c38028e5f1ba26e819e05ac8a3650759334a6d68020900000002ba6d17be00 | ||
1 output(s) for total of 35.094159322740 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6b66f94935cef8d980957c8c71c136b96f91d1513ea6aa5e3ed4c3983029fd4b | 35.094159322740 | 1497 of 0 | <8f> |
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": 1407,
"vin": [ {
"gen": {
"height": 1347
}
}
],
"vout": [ {
"amount": 35094159322740,
"target": {
"tagged_key": {
"key": "6b66f94935cef8d980957c8c71c136b96f91d1513ea6aa5e3ed4c3983029fd4b",
"view_tag": "8f"
}
}
}
],
"extra": [ 1, 175, 179, 203, 128, 226, 107, 185, 221, 23, 192, 1, 116, 195, 128, 40, 229, 241, 186, 38, 232, 25, 224, 90, 200, 163, 101, 7, 89, 51, 74, 109, 104, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}