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: 4ba54b84de8f2a8a9e8f3e96ce3c3ccdefe5ee552ce0730b2b64f22e101aa2e3
Tx prefix hash: f579a427bdea440df0a65414878d161249ac2e3f8374a291a58c945c640a9db9
Tx public key: 87ee66b238ca37bcbe9765c1edf43d3d28ccd943188fc34a8bfb2cb7cac427c3
| Timestamp: 1779854647 | Timestamp [UTC]: 2026-05-27 04:04:07 | Age [y:d:h:m:s]: 00:012:22:45:41 |
| Block: 2598 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5320 | RingCT/type: yes/0 |
| Extra: 0187ee66b238ca37bcbe9765c1edf43d3d28ccd943188fc34a8bfb2cb7cac427c302090000000226697be300 | ||
1 output(s) for total of 35.010521134111 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3e40d9738aec8a470ebad54c0e70468ba3561e6389ad8bc4889de16dad5e1580 | 35.010521134111 | 3058 of 0 | <bc> |
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": 2658,
"vin": [ {
"gen": {
"height": 2598
}
}
],
"vout": [ {
"amount": 35010521134111,
"target": {
"tagged_key": {
"key": "3e40d9738aec8a470ebad54c0e70468ba3561e6389ad8bc4889de16dad5e1580",
"view_tag": "bc"
}
}
}
],
"extra": [ 1, 135, 238, 102, 178, 56, 202, 55, 188, 190, 151, 101, 193, 237, 244, 61, 61, 40, 204, 217, 67, 24, 143, 195, 74, 139, 251, 44, 183, 202, 196, 39, 195, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}