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: e8f313a5126c93d6964578e20a7fc3b37516a28e93feec14880d84d24c7b8abd
Tx prefix hash: 17b82ba1e82e47d6d5c6e1934778a59404baa5a95eb93300e335f0155905bca6
Tx public key: 7098b8d1c46c4e6a4282f6feac06764b8fd68a80ea6aea96922162bfb3a0e5ee
| Timestamp: 1779636526 | Timestamp [UTC]: 2026-05-24 15:28:46 | Age [y:d:h:m:s]: 00:015:10:07:11 |
| Block: 1121 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6765 | RingCT/type: yes/0 |
| Extra: 017098b8d1c46c4e6a4282f6feac06764b8fd68a80ea6aea96922162bfb3a0e5ee020900000001ba6d17be00 | ||
1 output(s) for total of 35.109290314202 HMNY
| stealth address | amount | amount idx | tag |
| 00: bb11bc880362e5ffb1c40f3fd1b1d8a319fb40595869e84925c22bfa3f59b56d | 35.109290314202 | 1261 of 0 | <cb> |
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": 1181,
"vin": [ {
"gen": {
"height": 1121
}
}
],
"vout": [ {
"amount": 35109290314202,
"target": {
"tagged_key": {
"key": "bb11bc880362e5ffb1c40f3fd1b1d8a319fb40595869e84925c22bfa3f59b56d",
"view_tag": "cb"
}
}
}
],
"extra": [ 1, 112, 152, 184, 209, 196, 108, 78, 106, 66, 130, 246, 254, 172, 6, 118, 75, 143, 214, 138, 128, 234, 106, 234, 150, 146, 33, 98, 191, 179, 160, 229, 238, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}