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: 02fa834d2fa2121e5813b1f3d83d157588d8f210534ea7b7f5c2fcf0e307fc76
Tx prefix hash: 4f5ce6c7be2521a7b40fe62e7175fad907bc49e9e856cac6284ea4cf56d1655a
Tx public key: 2b1f4cb7b2f09e3edca8c6ee26151b1a08e22677790814361dcf0afea19fda27
| Timestamp: 1779443155 | Timestamp [UTC]: 2026-05-22 09:45:55 | Age [y:d:h:m:s]: 00:017:15:50:02 |
| Block: 234 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7652 | RingCT/type: yes/0 |
| Extra: 012b1f4cb7b2f09e3edca8c6ee26151b1a08e22677790814361dcf0afea19fda270209000000024438f87f00 | ||
1 output(s) for total of 35.168739182709 HMNY
| stealth address | amount | amount idx | tag |
| 00: aad15109f6bc723e63476008ebdb3d5914e0af3564c2d857d0c73dd2e0ef1104 | 35.168739182709 | 230 of 0 | <33> |
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": 294,
"vin": [ {
"gen": {
"height": 234
}
}
],
"vout": [ {
"amount": 35168739182709,
"target": {
"tagged_key": {
"key": "aad15109f6bc723e63476008ebdb3d5914e0af3564c2d857d0c73dd2e0ef1104",
"view_tag": "33"
}
}
}
],
"extra": [ 1, 43, 31, 76, 183, 178, 240, 158, 62, 220, 168, 198, 238, 38, 21, 27, 26, 8, 226, 38, 119, 121, 8, 20, 54, 29, 207, 10, 254, 161, 159, 218, 39, 2, 9, 0, 0, 0, 2, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}