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: be96a6c8002191c4c24ec984674f0f6372376ef3860fb8764aba43e99026d4cd
Tx prefix hash: eb19b0e11babca07bae8258c79b275979aca7fe56f22fd8e3e9e9651f1d1a1b6
Tx public key: 65ebd3f66fe474e8dedab94a1f9d37e12a7b50d343d589ebd91fc7b132f8b793
| Timestamp: 1781006762 | Timestamp [UTC]: 2026-06-09 12:06:02 | Age [y:d:h:m:s]: 00:005:23:07:58 |
| Block: 8564 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 181 | RingCT/type: yes/0 |
| Extra: 0165ebd3f66fe474e8dedab94a1f9d37e12a7b50d343d589ebd91fc7b132f8b793020900000009e49593ff00 | ||
1 output(s) for total of 34.614385700780 HMNY
| stealth address | amount | amount idx | tag |
| 00: f0a17dc1fa42cb265ec0cbb87131b582306085f71589a26c66517bf925cb188d | 34.614385700780 | 10574 of 0 | <80> |
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": 8624,
"vin": [ {
"gen": {
"height": 8564
}
}
],
"vout": [ {
"amount": 34614385700780,
"target": {
"tagged_key": {
"key": "f0a17dc1fa42cb265ec0cbb87131b582306085f71589a26c66517bf925cb188d",
"view_tag": "80"
}
}
}
],
"extra": [ 1, 101, 235, 211, 246, 111, 228, 116, 232, 222, 218, 185, 74, 31, 157, 55, 225, 42, 123, 80, 211, 67, 213, 137, 235, 217, 31, 199, 177, 50, 248, 183, 147, 2, 9, 0, 0, 0, 9, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}