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: c65f1ec7d671510d22291a7c9be9a9f229baf1300cf778a2388cf1f1f8de0eac
Tx prefix hash: b7e97022596908569b2d508cbb823c720c35ee3f0be53a7c767dd53dd3e515af
Tx public key: eebfd4b3efa023d6e72d9b7074f435d45568a6d5c1ce7b3d3e82a3200c358d99
| Timestamp: 1779444822 | Timestamp [UTC]: 2026-05-22 10:13:42 | Age [y:d:h:m:s]: 00:017:15:22:15 |
| Block: 262 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7624 | RingCT/type: yes/0 |
| Extra: 01eebfd4b3efa023d6e72d9b7074f435d45568a6d5c1ce7b3d3e82a3200c358d990209000000014438f87f00 | ||
1 output(s) for total of 35.166861017766 HMNY
| stealth address | amount | amount idx | tag |
| 00: ac2f0b171eff81b1d90cad8342e4c9e4977763ce28e93d4f05febef46e363439 | 35.166861017766 | 258 of 0 | <ea> |
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": 322,
"vin": [ {
"gen": {
"height": 262
}
}
],
"vout": [ {
"amount": 35166861017766,
"target": {
"tagged_key": {
"key": "ac2f0b171eff81b1d90cad8342e4c9e4977763ce28e93d4f05febef46e363439",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 238, 191, 212, 179, 239, 160, 35, 214, 231, 45, 155, 112, 116, 244, 53, 212, 85, 104, 166, 213, 193, 206, 123, 61, 62, 130, 163, 32, 12, 53, 141, 153, 2, 9, 0, 0, 0, 1, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}