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: 2351bfc6ed82f275d9b9bce85d6833a5fd748a77f7261062eea6fb37c0d5e2b0
Tx prefix hash: e6c35326ab0f6556b51ac1e431befee9dee612891b7e41c19fbf94886cc77654
Tx public key: 518f9f5242b2b40a8fe723ec6a8780cebb7c3de7c18c84c0f3a33208a36df303
| Timestamp: 1779447838 | Timestamp [UTC]: 2026-05-22 11:03:58 | Age [y:d:h:m:s]: 00:017:14:31:59 |
| Block: 291 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7595 | RingCT/type: yes/0 |
| Extra: 01518f9f5242b2b40a8fe723ec6a8780cebb7c3de7c18c84c0f3a33208a36df3030209000000014438f87f00 | ||
1 output(s) for total of 35.164915881243 HMNY
| stealth address | amount | amount idx | tag |
| 00: f4ca5ed302a653d12ebe2030fe8389515d5dcfd66e8c773024ce56c31b6d7383 | 35.164915881243 | 287 of 0 | <19> |
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": 351,
"vin": [ {
"gen": {
"height": 291
}
}
],
"vout": [ {
"amount": 35164915881243,
"target": {
"tagged_key": {
"key": "f4ca5ed302a653d12ebe2030fe8389515d5dcfd66e8c773024ce56c31b6d7383",
"view_tag": "19"
}
}
}
],
"extra": [ 1, 81, 143, 159, 82, 66, 178, 180, 10, 143, 231, 35, 236, 106, 135, 128, 206, 187, 124, 61, 231, 193, 140, 132, 192, 243, 163, 50, 8, 163, 109, 243, 3, 2, 9, 0, 0, 0, 1, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}