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: 40bdfd07638f09a8d2bceb5fb7e394ee6903bad79ec5247a1c95f872a2da7058
Tx prefix hash: 822c7fd2ac647f9988e5039eb1f6e657db7282f65f867cccad0a5024d8689ad2
Tx public key: 208a17c50c2c2a0929c345ee239d6af89e1f0f1b45654df03ce8eae56e3b3b09
| Timestamp: 1779856950 | Timestamp [UTC]: 2026-05-27 04:42:30 | Age [y:d:h:m:s]: 00:012:20:04:17 |
| Block: 2627 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5259 | RingCT/type: yes/0 |
| Extra: 01208a17c50c2c2a0929c345ee239d6af89e1f0f1b45654df03ce8eae56e3b3b0902090000000226697be300 | ||
1 output(s) for total of 35.014389045002 HMNY
| stealth address | amount | amount idx | tag |
| 00: 843d9d7a93a5ce8011ac29315064bea3b72f852edaee8119a2e00d41ee3bee10 | 35.014389045002 | 3093 of 0 | <57> |
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": 2687,
"vin": [ {
"gen": {
"height": 2627
}
}
],
"vout": [ {
"amount": 35014389045002,
"target": {
"tagged_key": {
"key": "843d9d7a93a5ce8011ac29315064bea3b72f852edaee8119a2e00d41ee3bee10",
"view_tag": "57"
}
}
}
],
"extra": [ 1, 32, 138, 23, 197, 12, 44, 42, 9, 41, 195, 69, 238, 35, 157, 106, 248, 158, 31, 15, 27, 69, 101, 77, 240, 60, 232, 234, 229, 110, 59, 59, 9, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}