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: 27a1379fdbb7d9156bf7e9ec84b3104c191451e1a80ab1e71c64d9b3b9c56229
Tx prefix hash: f3054169937c3ca103a00fe626f01702daad75059414f3302adb5ae78383a825
Tx public key: 904bde02cf76eb31b281b19e5a60e72846ddaf5ca869dbb4d6213f1abb5beb14
| Timestamp: 1779635074 | Timestamp [UTC]: 2026-05-24 15:04:34 | Age [y:d:h:m:s]: 00:015:10:31:23 |
| Block: 1063 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6823 | RingCT/type: yes/0 |
| Extra: 01904bde02cf76eb31b281b19e5a60e72846ddaf5ca869dbb4d6213f1abb5beb14020900000001ba6d17be00 | ||
1 output(s) for total of 35.113174540850 HMNY
| stealth address | amount | amount idx | tag |
| 00: 87dced24591d10b98a8a42833976008e2d413c0196b91dacaae74163f05ef360 | 35.113174540850 | 1201 of 0 | <df> |
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": 1123,
"vin": [ {
"gen": {
"height": 1063
}
}
],
"vout": [ {
"amount": 35113174540850,
"target": {
"tagged_key": {
"key": "87dced24591d10b98a8a42833976008e2d413c0196b91dacaae74163f05ef360",
"view_tag": "df"
}
}
}
],
"extra": [ 1, 144, 75, 222, 2, 207, 118, 235, 49, 178, 129, 177, 158, 90, 96, 231, 40, 70, 221, 175, 92, 168, 105, 219, 180, 214, 33, 63, 26, 187, 91, 235, 20, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}