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: 92450c256d9baba60c5cfc18b835818081e581ee3593375f2c9d76bbbfb04f24
Tx prefix hash: 8e881ea1f1f6cb4eb70cefc9c7660fbea63dc131636879f0a1e91b95b062384c
Tx public key: 2bf3fff5bcce891a8c32a347edd8a2ae2102b72e48406aaacf2093608fd5b4c9
| Timestamp: 1780323016 | Timestamp [UTC]: 2026-06-01 14:10:16 | Age [y:d:h:m:s]: 00:007:10:36:31 |
| Block: 5041 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2845 | RingCT/type: yes/0 |
| Extra: 012bf3fff5bcce891a8c32a347edd8a2ae2102b72e48406aaacf2093608fd5b4c902090000004026697be300 | ||
1 output(s) for total of 34.847763600492 HMNY
| stealth address | amount | amount idx | tag |
| 00: 58a46ba98748a982a63d58abd0caf5307eac665ded89f3b3728f9534019f5801 | 34.847763600492 | 6416 of 0 | <c4> |
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": 5101,
"vin": [ {
"gen": {
"height": 5041
}
}
],
"vout": [ {
"amount": 34847763600492,
"target": {
"tagged_key": {
"key": "58a46ba98748a982a63d58abd0caf5307eac665ded89f3b3728f9534019f5801",
"view_tag": "c4"
}
}
}
],
"extra": [ 1, 43, 243, 255, 245, 188, 206, 137, 26, 140, 50, 163, 71, 237, 216, 162, 174, 33, 2, 183, 46, 72, 64, 106, 170, 207, 32, 147, 96, 143, 213, 180, 201, 2, 9, 0, 0, 0, 64, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}