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: 8c71204af2d858e3d5c9e9578c2ba385e29bc88aadae3246233e87e47abf056d
Tx prefix hash: 17557c1216949218a1fb27e89a92e6ba6354658a7faa003b3f8194b2cfecfe38
Tx public key: 935131b7aed7d4fcfd530d9fdffc3c41ac13b1e5b95c53c61f132f6bebc43e31
| Timestamp: 1779629083 | Timestamp [UTC]: 2026-05-24 13:24:43 | Age [y:d:h:m:s]: 00:015:11:22:04 |
| Block: 816 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7070 | RingCT/type: yes/0 |
| Extra: 01935131b7aed7d4fcfd530d9fdffc3c41ac13b1e5b95c53c61f132f6bebc43e31020900000001ba6d17be00 | ||
1 output(s) for total of 35.129720801087 HMNY
| stealth address | amount | amount idx | tag |
| 00: b07e0e817f5870fe70f2ee4be8a2d5ec12435c5bc0a8a46bab627c718954228f | 35.129720801087 | 948 of 0 | <32> |
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": 876,
"vin": [ {
"gen": {
"height": 816
}
}
],
"vout": [ {
"amount": 35129720801087,
"target": {
"tagged_key": {
"key": "b07e0e817f5870fe70f2ee4be8a2d5ec12435c5bc0a8a46bab627c718954228f",
"view_tag": "32"
}
}
}
],
"extra": [ 1, 147, 81, 49, 183, 174, 215, 212, 252, 253, 83, 13, 159, 223, 252, 60, 65, 172, 19, 177, 229, 185, 92, 83, 198, 31, 19, 47, 107, 235, 196, 62, 49, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}