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: 766c6472a20ac4e083510e8821fdf1756ee99edf016ca4afae5ce02359e71e33
Tx prefix hash: 30f14144b4b5a54e28ec10070339f3c93600e58b2b8e4550efd98b5e3006b338
Tx public key: 21423d711fd5932c0ef0ded611c07180d1efed19b2f44a97e6582c305a800c4e
| Timestamp: 1779913691 | Timestamp [UTC]: 2026-05-27 20:28:11 | Age [y:d:h:m:s]: 00:012:06:12:25 |
| Block: 3275 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4621 | RingCT/type: yes/0 |
| Extra: 0121423d711fd5932c0ef0ded611c07180d1efed19b2f44a97e6582c305a800c4e02090000000326697be300 | ||
1 output(s) for total of 34.965342055078 HMNY
| stealth address | amount | amount idx | tag |
| 00: ac57d5374adab45eb4d3ca2ea2211d99cdc6cd96cbd4c5c59240460422b53c46 | 34.965342055078 | 3931 of 0 | <4d> |
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": 3335,
"vin": [ {
"gen": {
"height": 3275
}
}
],
"vout": [ {
"amount": 34965342055078,
"target": {
"tagged_key": {
"key": "ac57d5374adab45eb4d3ca2ea2211d99cdc6cd96cbd4c5c59240460422b53c46",
"view_tag": "4d"
}
}
}
],
"extra": [ 1, 33, 66, 61, 113, 31, 213, 147, 44, 14, 240, 222, 214, 17, 192, 113, 128, 209, 239, 237, 25, 178, 244, 74, 151, 230, 88, 44, 48, 90, 128, 12, 78, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}