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: c769420310f2c5c1f7b09b6b3db0e3ce5014159f263df0145d06531a4e7aa97e
Tx prefix hash: 53c50fc0b251b6be5edc963b02252df93acf7effe41224cc0d0b95ba27eda77e
Tx public key: a01c1056fbad250ba5112309bffcf9cbbe5a17edffcfffe2a47c4bfc15f68f85
| Timestamp: 1779866066 | Timestamp [UTC]: 2026-05-27 07:14:26 | Age [y:d:h:m:s]: 00:012:17:08:43 |
| Block: 2744 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5142 | RingCT/type: yes/0 |
| Extra: 01a01c1056fbad250ba5112309bffcf9cbbe5a17edffcfffe2a47c4bfc15f68f8502090000000426697be300 | ||
1 output(s) for total of 35.000773000808 HMNY
| stealth address | amount | amount idx | tag |
| 00: a93e9178696201184e468d4250e7e315b875aa2ef7e02aab539714e59933faf3 | 35.000773000808 | 3242 of 0 | <75> |
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": 2804,
"vin": [ {
"gen": {
"height": 2744
}
}
],
"vout": [ {
"amount": 35000773000808,
"target": {
"tagged_key": {
"key": "a93e9178696201184e468d4250e7e315b875aa2ef7e02aab539714e59933faf3",
"view_tag": "75"
}
}
}
],
"extra": [ 1, 160, 28, 16, 86, 251, 173, 37, 11, 165, 17, 35, 9, 191, 252, 249, 203, 190, 90, 23, 237, 255, 207, 255, 226, 164, 124, 75, 252, 21, 246, 143, 133, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}