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: ee541dd0fc4088c3eeac4d9adfc2f01fc8d8718e9ba396d3765b448ca70f1d08
Tx prefix hash: 6c0f3f9c68608b2ff61d6ba3d75f55a3138af7964af1dac72e186d345a1dbabe
Tx public key: 7f0e94a8ca943b996f333a96d9abc2423e7e87fe1a323e9290b238dad6ebd8d6
| Timestamp: 1780799122 | Timestamp [UTC]: 2026-06-07 02:25:22 | Age [y:d:h:m:s]: 00:002:01:25:36 |
| Block: 6809 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1171 | RingCT/type: yes/0 |
| Extra: 017f0e94a8ca943b996f333a96d9abc2423e7e87fe1a323e9290b238dad6ebd8d6020900000004e49593ff00 | ||
1 output(s) for total of 34.730448042129 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7710f0534643359032adf77b892b2c613367d9ba756ad1fb3a4fc761b818aa64 | 34.730448042129 | 8407 of 0 | <00> |
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": 6869,
"vin": [ {
"gen": {
"height": 6809
}
}
],
"vout": [ {
"amount": 34730448042129,
"target": {
"tagged_key": {
"key": "7710f0534643359032adf77b892b2c613367d9ba756ad1fb3a4fc761b818aa64",
"view_tag": "00"
}
}
}
],
"extra": [ 1, 127, 14, 148, 168, 202, 148, 59, 153, 111, 51, 58, 150, 217, 171, 194, 66, 62, 126, 135, 254, 26, 50, 62, 146, 144, 178, 56, 218, 214, 235, 216, 214, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}