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: ad0e51b24ac5c19cc2518140922f8053637cae5cad4948635b3acfd90f42b78e
Tx prefix hash: 117fcdb1a3fc356e1ce47b8744b6676b552b65a81635370b043c1fa0cb14831b
Tx public key: 79d8e9bdafa72dc3385765d31c273770b3ef9b5acedc06dbc01b8653f976f382
| Timestamp: 1780902269 | Timestamp [UTC]: 2026-06-08 07:04:29 | Age [y:d:h:m:s]: 00:000:17:18:40 |
| Block: 7829 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 57 | RingCT/type: yes/0 |
| Extra: 0179d8e9bdafa72dc3385765d31c273770b3ef9b5acedc06dbc01b8653f976f3820209000000014a728a4c00 | ||
1 output(s) for total of 34.662945727731 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7485a3048e3e3251b5b04c469dc3e37683849c25e27303f99cf487c763cfd8f0 | 34.662945727731 | 9705 of 0 | <4a> |
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": 7889,
"vin": [ {
"gen": {
"height": 7829
}
}
],
"vout": [ {
"amount": 34662945727731,
"target": {
"tagged_key": {
"key": "7485a3048e3e3251b5b04c469dc3e37683849c25e27303f99cf487c763cfd8f0",
"view_tag": "4a"
}
}
}
],
"extra": [ 1, 121, 216, 233, 189, 175, 167, 45, 195, 56, 87, 101, 211, 28, 39, 55, 112, 179, 239, 155, 90, 206, 220, 6, 219, 192, 27, 134, 83, 249, 118, 243, 130, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}