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: 1858b4725aa275c6760b5d92a8fc5c9f28e736b16f2026598f58ba0a51497fd4
Tx prefix hash: 3fe97a82c1b84440db993f729bcb898e0239df30d129be0a76d95670bc34fc48
Tx public key: c3032c37a60e2a4965bd22fab3cb8c4ae0d2f5993d3787884af47150ad547998
| Timestamp: 1780012657 | Timestamp [UTC]: 2026-05-28 23:57:37 | Age [y:d:h:m:s]: 00:010:23:21:16 |
| Block: 4105 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3781 | RingCT/type: yes/0 |
| Extra: 01c3032c37a60e2a4965bd22fab3cb8c4ae0d2f5993d3787884af47150ad54799802090000000126697be300 | ||
1 output(s) for total of 34.910032183581 HMNY
| stealth address | amount | amount idx | tag |
| 00: f038dbbdd7b11ae75feef26473356789c173951d13e1786ff63c3d915fe1d017 | 34.910032183581 | 5112 of 0 | <c0> |
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": 4165,
"vin": [ {
"gen": {
"height": 4105
}
}
],
"vout": [ {
"amount": 34910032183581,
"target": {
"tagged_key": {
"key": "f038dbbdd7b11ae75feef26473356789c173951d13e1786ff63c3d915fe1d017",
"view_tag": "c0"
}
}
}
],
"extra": [ 1, 195, 3, 44, 55, 166, 14, 42, 73, 101, 189, 34, 250, 179, 203, 140, 74, 224, 210, 245, 153, 61, 55, 135, 136, 74, 244, 113, 80, 173, 84, 121, 152, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}