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: edda6c72592ed6fb09c47160250b2dd77ec34a1a6c7552aff821d51f8a53ac18
Tx prefix hash: e41efbfc9f0ce5ee4591a00ad65f75b4da29038b626f3b6d1c24c67072fcd425
Tx public key: e4033730688fd34aa56b21d58dc4cedddcd817e734f86197aba6c6229fb763d0
| Timestamp: 1779437863 | Timestamp [UTC]: 2026-05-22 08:17:43 | Age [y:d:h:m:s]: 00:017:18:32:05 |
| Block: 177 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7723 | RingCT/type: yes/0 |
| Extra: 01e4033730688fd34aa56b21d58dc4cedddcd817e734f86197aba6c6229fb763d0020900000001a662ed0300 | ||
1 output(s) for total of 35.172562899863 HMNY
| stealth address | amount | amount idx | tag |
| 00: f60f322a29750c27ed2f3d9c86b334cc78cfda98825ee4abac64c4cac5596702 | 35.172562899863 | 173 of 0 | <2e> |
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": 237,
"vin": [ {
"gen": {
"height": 177
}
}
],
"vout": [ {
"amount": 35172562899863,
"target": {
"tagged_key": {
"key": "f60f322a29750c27ed2f3d9c86b334cc78cfda98825ee4abac64c4cac5596702",
"view_tag": "2e"
}
}
}
],
"extra": [ 1, 228, 3, 55, 48, 104, 143, 211, 74, 165, 107, 33, 213, 141, 196, 206, 221, 220, 216, 23, 231, 52, 248, 97, 151, 171, 166, 198, 34, 159, 183, 99, 208, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}