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: a4f1d1e7c9fbef8cab03f503d417b80bd4daa658a34d260acd10b09f977cd32f
Tx prefix hash: 2dc375686954b22ffee562acb7bf434aa9fda01aa8323fbcd109e08ac3970265
Tx public key: 57ff2bb4c995e6437ecfb8f395ce820aaca69a9f02310a914ad1f0d92ed8a7ea
| Timestamp: 1780080102 | Timestamp [UTC]: 2026-05-29 18:41:42 | Age [y:d:h:m:s]: 00:010:06:54:15 |
| Block: 4754 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3132 | RingCT/type: yes/0 |
| Extra: 0157ff2bb4c995e6437ecfb8f395ce820aaca69a9f02310a914ad1f0d92ed8a7ea02090000000326697be300 | ||
1 output(s) for total of 34.866844822263 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8fe6aa26e308d81a3a9f8906c9f24b7472998e78f211c8f2f5952eb723fe373b | 34.866844822263 | 5975 of 0 | <77> |
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": 4814,
"vin": [ {
"gen": {
"height": 4754
}
}
],
"vout": [ {
"amount": 34866844822263,
"target": {
"tagged_key": {
"key": "8fe6aa26e308d81a3a9f8906c9f24b7472998e78f211c8f2f5952eb723fe373b",
"view_tag": "77"
}
}
}
],
"extra": [ 1, 87, 255, 43, 180, 201, 149, 230, 67, 126, 207, 184, 243, 149, 206, 130, 10, 172, 166, 154, 159, 2, 49, 10, 145, 74, 209, 240, 217, 46, 216, 167, 234, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}