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: adf988f8e6cf3ce1eee123343ebd27adf3f081e264acaed92530ac8390d1add3
Tx prefix hash: a9641637d4330fbe4d6d9a50929878bc537a956e2d7818b86c385b2fc2b06f96
Tx public key: eab2d867b7f2bd25db76935bce0f16ee98605ecd5132622049b4f2e8e633cc28
| Timestamp: 1779961715 | Timestamp [UTC]: 2026-05-28 09:48:35 | Age [y:d:h:m:s]: 00:011:14:58:12 |
| Block: 3768 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4118 | RingCT/type: yes/0 |
| Extra: 01eab2d867b7f2bd25db76935bce0f16ee98605ecd5132622049b4f2e8e633cc2802090000000726697be300 | ||
1 output(s) for total of 34.938999566209 HMNY
| stealth address | amount | amount idx | tag |
| 00: bbf4f5e35ce9ad9006ff336b37af99f59bb5763e8d1cc7fc036479c783a94d28 | 34.938999566209 | 4569 of 0 | <5d> |
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": 3828,
"vin": [ {
"gen": {
"height": 3768
}
}
],
"vout": [ {
"amount": 34938999566209,
"target": {
"tagged_key": {
"key": "bbf4f5e35ce9ad9006ff336b37af99f59bb5763e8d1cc7fc036479c783a94d28",
"view_tag": "5d"
}
}
}
],
"extra": [ 1, 234, 178, 216, 103, 183, 242, 189, 37, 219, 118, 147, 91, 206, 15, 22, 238, 152, 96, 94, 205, 81, 50, 98, 32, 73, 180, 242, 232, 230, 51, 204, 40, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}