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: 1f6d8172b391610775574c285672aa9a6afa257e8bc196b5e0e45c7a567c5b19
Tx prefix hash: 64c3d45400ee608587085ce998b144d22f5c04e066e7f445b00841a23122b3a8
Tx public key: 35ac9539d0b41876da7e33603738a101663f27dbc8f6517d07ef04000ff8e3b0
| Timestamp: 1779953745 | Timestamp [UTC]: 2026-05-28 07:35:45 | Age [y:d:h:m:s]: 00:011:20:15:13 |
| Block: 3657 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4308 | RingCT/type: yes/0 |
| Extra: 0135ac9539d0b41876da7e33603738a101663f27dbc8f6517d07ef04000ff8e3b002090000000126697be300 | ||
1 output(s) for total of 34.939875310351 HMNY
| stealth address | amount | amount idx | tag |
| 00: 695e714707a3514bcd8e460dc021262cf3d81c4b6da83b071bd9c3f295dd220a | 34.939875310351 | 4419 of 0 | <fd> |
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": 3717,
"vin": [ {
"gen": {
"height": 3657
}
}
],
"vout": [ {
"amount": 34939875310351,
"target": {
"tagged_key": {
"key": "695e714707a3514bcd8e460dc021262cf3d81c4b6da83b071bd9c3f295dd220a",
"view_tag": "fd"
}
}
}
],
"extra": [ 1, 53, 172, 149, 57, 208, 180, 24, 118, 218, 126, 51, 96, 55, 56, 161, 1, 102, 63, 39, 219, 200, 246, 81, 125, 7, 239, 4, 0, 15, 248, 227, 176, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}