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: cda09fbb06e5bb2e54e7c9b5674df6b5043389e2af40c37c32857529b7825033
Tx prefix hash: e20008bc56a4c0a0d1321d3015428e7237f9ff65cdd3eb325dcb8691e6f796ce
Tx public key: 1aa191da4b5dbf96af5b9955f3962f7e34980948fd150b84d3af79fc5ebc7ee6
| Timestamp: 1779772459 | Timestamp [UTC]: 2026-05-26 05:14:19 | Age [y:d:h:m:s]: 00:013:20:21:38 |
| Block: 2030 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5856 | RingCT/type: yes/0 |
| Extra: 011aa191da4b5dbf96af5b9955f3962f7e34980948fd150b84d3af79fc5ebc7ee602090000000126697be300 | ||
1 output(s) for total of 35.048471212799 HMNY
| stealth address | amount | amount idx | tag |
| 00: 107043c969a5696206183201e9eed46c824b08ad6b6b0b8733f2d0370758f591 | 35.048471212799 | 2320 of 0 | <0e> |
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": 2090,
"vin": [ {
"gen": {
"height": 2030
}
}
],
"vout": [ {
"amount": 35048471212799,
"target": {
"tagged_key": {
"key": "107043c969a5696206183201e9eed46c824b08ad6b6b0b8733f2d0370758f591",
"view_tag": "0e"
}
}
}
],
"extra": [ 1, 26, 161, 145, 218, 75, 93, 191, 150, 175, 91, 153, 85, 243, 150, 47, 126, 52, 152, 9, 72, 253, 21, 11, 132, 211, 175, 121, 252, 94, 188, 126, 230, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}