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: 594f317453e2b729a93924e19f610a089d9efad85cd7b3b986e8279e7a087aad
Tx prefix hash: 5e67301a7047ce4764cf0e047038091366996815071f6cbb406943e38d394ae3
Tx public key: ede8165b4a7a3a8d51ff536e44625c45de8972ddd3ab90324825ead0ea290ea8
| Timestamp: 1780825891 | Timestamp [UTC]: 2026-06-07 09:51:31 | Age [y:d:h:m:s]: 00:001:18:41:31 |
| Block: 7261 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 768 | RingCT/type: yes/0 |
| Extra: 01ede8165b4a7a3a8d51ff536e44625c45de8972ddd3ab90324825ead0ea290ea8020900000001e49593ff00 | ||
1 output(s) for total of 34.700519047846 HMNY
| stealth address | amount | amount idx | tag |
| 00: cac50a1525a9985078259fe855f12f491161787d3ad06b02dc5be7af5d3f71b4 | 34.700519047846 | 8941 of 0 | <40> |
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": 7321,
"vin": [ {
"gen": {
"height": 7261
}
}
],
"vout": [ {
"amount": 34700519047846,
"target": {
"tagged_key": {
"key": "cac50a1525a9985078259fe855f12f491161787d3ad06b02dc5be7af5d3f71b4",
"view_tag": "40"
}
}
}
],
"extra": [ 1, 237, 232, 22, 91, 74, 122, 58, 141, 81, 255, 83, 110, 68, 98, 92, 69, 222, 137, 114, 221, 211, 171, 144, 50, 72, 37, 234, 208, 234, 41, 14, 168, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}