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: 55cd3223c6715fa4f364ce954461b04debc058e54622d76d1f6a03d077fce093
Tx prefix hash: e19c6c1ccb2e44c42438ab03c478d460164fde69f09e0cdb2b44a8fbe06a43ed
Tx public key: 8f6c60fb9fd1f4de8200940598ba6d6a48caea5ec5c4a62ad9a04bff14b9f5a5
| Timestamp: 1781004371 | Timestamp [UTC]: 2026-06-09 11:26:11 | Age [y:d:h:m:s]: 00:000:03:22:44 |
| Block: 8509 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 133 | RingCT/type: yes/0 |
| Extra: 018f6c60fb9fd1f4de8200940598ba6d6a48caea5ec5c4a62ad9a04bff14b9f5a5020900000001e49593ff00 | ||
1 output(s) for total of 34.618017088282 HMNY
| stealth address | amount | amount idx | tag |
| 00: 33b8cc87b1fe31a3633022d780297e075a2d912d910d207e1e9e683c89ccde42 | 34.618017088282 | 10511 of 0 | <b1> |
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": 8569,
"vin": [ {
"gen": {
"height": 8509
}
}
],
"vout": [ {
"amount": 34618017088282,
"target": {
"tagged_key": {
"key": "33b8cc87b1fe31a3633022d780297e075a2d912d910d207e1e9e683c89ccde42",
"view_tag": "b1"
}
}
}
],
"extra": [ 1, 143, 108, 96, 251, 159, 209, 244, 222, 130, 0, 148, 5, 152, 186, 109, 106, 72, 202, 234, 94, 197, 196, 166, 42, 217, 160, 75, 255, 20, 185, 245, 165, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}