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: 07a83244653d280ec6d57214c50f5f4bf687ed8ce762a6872770c08daf8b91e5
Tx prefix hash: 9c00b039ab138669ad00e11dc5cc80a13920e9bd099176b23bdebe37ad03ec3b
Tx public key: e1e65b48b05b922afe2a9b92fec6d877051021ad98927beb84e7839fb9fe8b28
| Timestamp: 1780323195 | Timestamp [UTC]: 2026-06-01 14:13:15 | Age [y:d:h:m:s]: 00:007:10:33:32 |
| Block: 5076 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2810 | RingCT/type: yes/0 |
| Extra: 01e1e65b48b05b922afe2a9b92fec6d877051021ad98927beb84e7839fb9fe8b2802090000003f26697be300 | ||
1 output(s) for total of 34.845437336723 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5509d0e35ca651b9a8741d31c60c1789598c7caedb7ea909b7ae3622ff171c0f | 34.845437336723 | 6451 of 0 | <a6> |
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": 5136,
"vin": [ {
"gen": {
"height": 5076
}
}
],
"vout": [ {
"amount": 34845437336723,
"target": {
"tagged_key": {
"key": "5509d0e35ca651b9a8741d31c60c1789598c7caedb7ea909b7ae3622ff171c0f",
"view_tag": "a6"
}
}
}
],
"extra": [ 1, 225, 230, 91, 72, 176, 91, 146, 42, 254, 42, 155, 146, 254, 198, 216, 119, 5, 16, 33, 173, 152, 146, 123, 235, 132, 231, 131, 159, 185, 254, 139, 40, 2, 9, 0, 0, 0, 63, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}