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: f2829ba29dd24c7bcb2079f5bb49e3246ae6c435068a9284417ed56555e73323
Tx prefix hash: 54d43fbc4eefc7cc823d99d1d2762a9163fcfa7189f7e9882754ded2d05c48ed
Tx public key: 50960c4106f92fc9c4294dfb2537baa40e841b4c8e15e5a23a5ae245b502e545
| Timestamp: 1779937202 | Timestamp [UTC]: 2026-05-28 03:00:02 | Age [y:d:h:m:s]: 00:011:22:35:55 |
| Block: 3452 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4434 | RingCT/type: yes/0 |
| Extra: 0150960c4106f92fc9c4294dfb2537baa40e841b4c8e15e5a23a5ae245b502e54502090000000526697be300 | ||
1 output(s) for total of 34.953539711941 HMNY
| stealth address | amount | amount idx | tag |
| 00: c3dd9d7d59b572be9f48ee0e7ea3242abdd6ed4c17a9c95728d3514d14baa7fe | 34.953539711941 | 4169 of 0 | <9c> |
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": 3512,
"vin": [ {
"gen": {
"height": 3452
}
}
],
"vout": [ {
"amount": 34953539711941,
"target": {
"tagged_key": {
"key": "c3dd9d7d59b572be9f48ee0e7ea3242abdd6ed4c17a9c95728d3514d14baa7fe",
"view_tag": "9c"
}
}
}
],
"extra": [ 1, 80, 150, 12, 65, 6, 249, 47, 201, 196, 41, 77, 251, 37, 55, 186, 164, 14, 132, 27, 76, 142, 21, 229, 162, 58, 90, 226, 69, 181, 2, 229, 69, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}