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: 23e4ca0f56abc678d553ec182b02a0283764614be43ed4d4989ee723f2b35af7
Tx prefix hash: 1371e9724e8640e13a66611ebec79b1325bc4760e0e286b5566c02b739351941
Tx public key: d87ff083c3fdc3c24ca186cdcb3dfb85c9cb6b7514269f807ffeea83bd757874
| Timestamp: 1780088579 | Timestamp [UTC]: 2026-05-29 21:02:59 | Age [y:d:h:m:s]: 00:010:04:32:58 |
| Block: 4830 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3056 | RingCT/type: yes/0 |
| Extra: 01d87ff083c3fdc3c24ca186cdcb3dfb85c9cb6b7514269f807ffeea83bd75787402090000000126697be300 | ||
1 output(s) for total of 34.865210938365 HMNY
| stealth address | amount | amount idx | tag |
| 00: 840e041b4815b4169dc9ff2c01304aca29c00eceb8aff622dd2a072786963c9b | 34.865210938365 | 6078 of 0 | <28> |
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": 4890,
"vin": [ {
"gen": {
"height": 4830
}
}
],
"vout": [ {
"amount": 34865210938365,
"target": {
"tagged_key": {
"key": "840e041b4815b4169dc9ff2c01304aca29c00eceb8aff622dd2a072786963c9b",
"view_tag": "28"
}
}
}
],
"extra": [ 1, 216, 127, 240, 131, 195, 253, 195, 194, 76, 161, 134, 205, 203, 61, 251, 133, 201, 203, 107, 117, 20, 38, 159, 128, 127, 254, 234, 131, 189, 117, 120, 116, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}