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: da0f13beff71b9c88ffbf599b512defae92baf51927a4caeeceba408dc11ad9e
Tx prefix hash: 866ef84a41ffc0a626fe9fa7f221bdcdcc726c802f1141b5afefeb5172552ebc
Tx public key: ccdbb96d8f997efea0d4ebcb2ff04764cf276bb62c2b6d24c96406b7186f8430
| Timestamp: 1779977239 | Timestamp [UTC]: 2026-05-28 14:07:19 | Age [y:d:h:m:s]: 00:012:03:01:44 |
| Block: 3894 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4841 | RingCT/type: yes/0 |
| Extra: 01ccdbb96d8f997efea0d4ebcb2ff04764cf276bb62c2b6d24c96406b7186f843002090000000426697be300 | ||
1 output(s) for total of 34.924084586546 HMNY
| stealth address | amount | amount idx | tag |
| 00: 174e97de34cd3305b818b9e18452f3e61b270dfa3367c6d4938e71404b2a6dda | 34.924084586546 | 4769 of 0 | <8c> |
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": 3954,
"vin": [ {
"gen": {
"height": 3894
}
}
],
"vout": [ {
"amount": 34924084586546,
"target": {
"tagged_key": {
"key": "174e97de34cd3305b818b9e18452f3e61b270dfa3367c6d4938e71404b2a6dda",
"view_tag": "8c"
}
}
}
],
"extra": [ 1, 204, 219, 185, 109, 143, 153, 126, 254, 160, 212, 235, 203, 47, 240, 71, 100, 207, 39, 107, 182, 44, 43, 109, 36, 201, 100, 6, 183, 24, 111, 132, 48, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}