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: dd64c3daf930d35d15b4c23801d0d5ce9ddfc534a8a3bc856f8014ef03246925
Tx prefix hash: 6eb4c15c1afbb70135ff00d6afd14a9adf4fe6660f82692f60385cf6cb07c7df
Tx public key: 0edfe4389104e13f0f4b7f05900944adb63cb4aa52e44586bdeab2693ea18836
| Timestamp: 1779456630 | Timestamp [UTC]: 2026-05-22 13:30:30 | Age [y:d:h:m:s]: 00:017:12:05:27 |
| Block: 392 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7494 | RingCT/type: yes/0 |
| Extra: 010edfe4389104e13f0f4b7f05900944adb63cb4aa52e44586bdeab2693ea1883602090000000193369e7d00 | ||
1 output(s) for total of 35.158142280068 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3e0a7e86d6443ea05aaa18b92c518ba5e06cb20e32a4eeeb74206bb953cbdfd9 | 35.158142280068 | 392 of 0 | <71> |
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": 452,
"vin": [ {
"gen": {
"height": 392
}
}
],
"vout": [ {
"amount": 35158142280068,
"target": {
"tagged_key": {
"key": "3e0a7e86d6443ea05aaa18b92c518ba5e06cb20e32a4eeeb74206bb953cbdfd9",
"view_tag": "71"
}
}
}
],
"extra": [ 1, 14, 223, 228, 56, 145, 4, 225, 63, 15, 75, 127, 5, 144, 9, 68, 173, 182, 60, 180, 170, 82, 228, 69, 134, 189, 234, 178, 105, 62, 161, 136, 54, 2, 9, 0, 0, 0, 1, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}