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: bec9d79965e480734c9711e47aaa2ba7af45ce87eb5a5b07510dbf88d720436e
Tx prefix hash: d59601e2668c2b8f902ec0fd360aad322ac2c83ea0576aab7cf02bc997df3b57
Tx public key: 0de4b8c89fa25a9d35c9d4cd487cd6918962abe912d987ac64edeace221c8581
| Timestamp: 1780085846 | Timestamp [UTC]: 2026-05-29 20:17:26 | Age [y:d:h:m:s]: 00:016:12:02:09 |
| Block: 4812 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3933 | RingCT/type: yes/0 |
| Extra: 010de4b8c89fa25a9d35c9d4cd487cd6918962abe912d987ac64edeace221c858102090000000326697be300 | ||
1 output(s) for total of 34.862987844659 HMNY
| stealth address | amount | amount idx | tag |
| 00: ff7facf0ee0a323f16c582fc62a4c7b17aa3b42a26a7f728b2c147d11e4f4465 | 34.862987844659 | 6052 of 0 | <5a> |
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": 4872,
"vin": [ {
"gen": {
"height": 4812
}
}
],
"vout": [ {
"amount": 34862987844659,
"target": {
"tagged_key": {
"key": "ff7facf0ee0a323f16c582fc62a4c7b17aa3b42a26a7f728b2c147d11e4f4465",
"view_tag": "5a"
}
}
}
],
"extra": [ 1, 13, 228, 184, 200, 159, 162, 90, 157, 53, 201, 212, 205, 72, 124, 214, 145, 137, 98, 171, 233, 18, 217, 135, 172, 100, 237, 234, 206, 34, 28, 133, 129, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}