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: e4e67c0593747c18f2146f0facd01d9962e966b7cc559d49592a9736007b6115
Tx prefix hash: 9018ca195c6367c65a7a94d6a483d8259e034bb67627530635ebe8bbcffe54f4
Tx public key: c74f977c5e3ffbb92194068142467b4b67f2fc4a2e99ed94a139fc6ad5a5a3ad
| Timestamp: 1780996577 | Timestamp [UTC]: 2026-06-09 09:16:17 | Age [y:d:h:m:s]: 00:000:05:32:38 |
| Block: 8353 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 302 | RingCT/type: yes/0 |
| Extra: 01c74f977c5e3ffbb92194068142467b4b67f2fc4a2e99ed94a139fc6ad5a5a3ad020900000001e49593ff00 | ||
1 output(s) for total of 34.628319096593 HMNY
| stealth address | amount | amount idx | tag |
| 00: a127712cfb7bca6772fa63423d7e0ad584e92a065764b03a79813e0028db7092 | 34.628319096593 | 10329 of 0 | <f2> |
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": 8413,
"vin": [ {
"gen": {
"height": 8353
}
}
],
"vout": [ {
"amount": 34628319096593,
"target": {
"tagged_key": {
"key": "a127712cfb7bca6772fa63423d7e0ad584e92a065764b03a79813e0028db7092",
"view_tag": "f2"
}
}
}
],
"extra": [ 1, 199, 79, 151, 124, 94, 63, 251, 185, 33, 148, 6, 129, 66, 70, 123, 75, 103, 242, 252, 74, 46, 153, 237, 148, 161, 57, 252, 106, 213, 165, 163, 173, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}