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: c630783a937e37dd224fa475f69012291a7533f0e8500b64e326af307da655bb
Tx prefix hash: 0883236ac71a46744e2e665d4f66bbddfcc2f08f91bed7e51aa50813a03078fd
Tx public key: 0dd757cdf16664b9082290a38b1ea53900087b5bb2449eba881e27591b253b8c
| Timestamp: 1779775814 | Timestamp [UTC]: 2026-05-26 06:10:14 | Age [y:d:h:m:s]: 00:013:18:36:33 |
| Block: 2065 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5821 | RingCT/type: yes/0 |
| Extra: 010dd757cdf16664b9082290a38b1ea53900087b5bb2449eba881e27591b253b8c02090000000226697be300 | ||
1 output(s) for total of 35.046131550786 HMNY
| stealth address | amount | amount idx | tag |
| 00: 050e1544b955e97c7b94994fb434b05dfb061b2d76c7091a21e3efe1d8aabc51 | 35.046131550786 | 2367 of 0 | <50> |
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": 2125,
"vin": [ {
"gen": {
"height": 2065
}
}
],
"vout": [ {
"amount": 35046131550786,
"target": {
"tagged_key": {
"key": "050e1544b955e97c7b94994fb434b05dfb061b2d76c7091a21e3efe1d8aabc51",
"view_tag": "50"
}
}
}
],
"extra": [ 1, 13, 215, 87, 205, 241, 102, 100, 185, 8, 34, 144, 163, 139, 30, 165, 57, 0, 8, 123, 91, 178, 68, 158, 186, 136, 30, 39, 89, 27, 37, 59, 140, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}