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: 39eb7909f4486eff72e32bc42db33cdab9281977b8580306263dadd7a59ba16c
Tx prefix hash: 7f21b2cb76007a1e50297eef7c312fa80ae1e975bee221b9b97f50fe56aff255
Tx public key: 61d15c5addc5fcf1f3365f3763f513ffcaa1db3bd66005e15375313b003d7c67
| Timestamp: 1780693618 | Timestamp [UTC]: 2026-06-05 21:06:58 | Age [y:d:h:m:s]: 00:009:11:12:37 |
| Block: 5881 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2864 | RingCT/type: yes/0 |
| Extra: 0161d15c5addc5fcf1f3365f3763f513ffcaa1db3bd66005e15375313b003d7c67020900000001e49593ff00 | ||
1 output(s) for total of 34.791976109047 HMNY
| stealth address | amount | amount idx | tag |
| 00: be3d41b86ee61ac2c4cf4ed268b3bb8288c57ff43219ce35cef60b3dd2c250cc | 34.791976109047 | 7340 of 0 | <5a> |
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": 5941,
"vin": [ {
"gen": {
"height": 5881
}
}
],
"vout": [ {
"amount": 34791976109047,
"target": {
"tagged_key": {
"key": "be3d41b86ee61ac2c4cf4ed268b3bb8288c57ff43219ce35cef60b3dd2c250cc",
"view_tag": "5a"
}
}
}
],
"extra": [ 1, 97, 209, 92, 90, 221, 197, 252, 241, 243, 54, 95, 55, 99, 245, 19, 255, 202, 161, 219, 59, 214, 96, 5, 225, 83, 117, 49, 59, 0, 61, 124, 103, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}