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: 1d86d9b35920568ac57ac82d26918e0d9a307662bb20f04a3929982df868e14d
Tx prefix hash: ee18eea7bf8e5d9fef6bcb0d39ec9bf591e676afdec7f96f8a72eb23a5cb2474
Tx public key: 618dc841e38555e917bc4fb8fbed4dc21815c34681bb0ab3b45a2f1f42eae8d3
| Timestamp: 1779793114 | Timestamp [UTC]: 2026-05-26 10:58:34 | Age [y:d:h:m:s]: 00:013:16:40:16 |
| Block: 2245 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5702 | RingCT/type: yes/0 |
| Extra: 01618dc841e38555e917bc4fb8fbed4dc21815c34681bb0ab3b45a2f1f42eae8d302090000000226697be300 | ||
1 output(s) for total of 35.038308670134 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1db4bb6ea5f74162cbac3c385dd95f6f56fe0dfc5a542e1fa2b2e43f4cfdf02f | 35.038308670134 | 2603 of 0 | <74> |
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": 2305,
"vin": [ {
"gen": {
"height": 2245
}
}
],
"vout": [ {
"amount": 35038308670134,
"target": {
"tagged_key": {
"key": "1db4bb6ea5f74162cbac3c385dd95f6f56fe0dfc5a542e1fa2b2e43f4cfdf02f",
"view_tag": "74"
}
}
}
],
"extra": [ 1, 97, 141, 200, 65, 227, 133, 85, 233, 23, 188, 79, 184, 251, 237, 77, 194, 24, 21, 195, 70, 129, 187, 10, 179, 180, 90, 47, 31, 66, 234, 232, 211, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}