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: ce954751dde2be8bc47ca47023098a5a6c175faf598a13050122c1a295ddeacf
Tx prefix hash: 514f8b26b8147dbb26846d6f5a1bd6cda9b40a170f6d98f93cd9ca5bdeec6a92
Tx public key: d496b2ea288f0d8d571d7e87b98f049f9df276ced4cfa2bba2e391e1d8be4b79
| Timestamp: 1779969434 | Timestamp [UTC]: 2026-05-28 11:57:14 | Age [y:d:h:m:s]: 00:011:13:38:43 |
| Block: 3835 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4051 | RingCT/type: yes/0 |
| Extra: 01d496b2ea288f0d8d571d7e87b98f049f9df276ced4cfa2bba2e391e1d8be4b7902090000000326697be300 | ||
1 output(s) for total of 34.928014943333 HMNY
| stealth address | amount | amount idx | tag |
| 00: 00c3f31e2a2a3a780e452629c97f66d39eb91c1871ec0131bf14f3149a3451a8 | 34.928014943333 | 4675 of 0 | <f5> |
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": 3895,
"vin": [ {
"gen": {
"height": 3835
}
}
],
"vout": [ {
"amount": 34928014943333,
"target": {
"tagged_key": {
"key": "00c3f31e2a2a3a780e452629c97f66d39eb91c1871ec0131bf14f3149a3451a8",
"view_tag": "f5"
}
}
}
],
"extra": [ 1, 212, 150, 178, 234, 40, 143, 13, 141, 87, 29, 126, 135, 185, 143, 4, 159, 157, 242, 118, 206, 212, 207, 162, 187, 162, 227, 145, 225, 216, 190, 75, 121, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}