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: a9a60ad5668a29b1fa9f10544478fb2ba496b9ccc291600cb3411f17e0d6d48f
Tx prefix hash: 7a5d31aed9c72830f4951500c346e692d450d90615cb7f3534af0e66fbd7ff96
Tx public key: 42e58b3bb4de7a8fe4461e9034e87315787fbae77ac860c06bd73600d97f34ec
| Timestamp: 1780692077 | Timestamp [UTC]: 2026-06-05 20:41:17 | Age [y:d:h:m:s]: 00:003:02:37:36 |
| Block: 5769 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2117 | RingCT/type: yes/0 |
| Extra: 0142e58b3bb4de7a8fe4461e9034e87315787fbae77ac860c06bd73600d97f34ec020900000001e49593ff00 | ||
1 output(s) for total of 34.799409277999 HMNY
| stealth address | amount | amount idx | tag |
| 00: f8272b7ff43a58686a1cb67fa5261fed669847fd8bbcd3116896db0dce2e4a08 | 34.799409277999 | 7224 of 0 | <83> |
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": 5829,
"vin": [ {
"gen": {
"height": 5769
}
}
],
"vout": [ {
"amount": 34799409277999,
"target": {
"tagged_key": {
"key": "f8272b7ff43a58686a1cb67fa5261fed669847fd8bbcd3116896db0dce2e4a08",
"view_tag": "83"
}
}
}
],
"extra": [ 1, 66, 229, 139, 59, 180, 222, 122, 143, 228, 70, 30, 144, 52, 232, 115, 21, 120, 127, 186, 231, 122, 200, 96, 192, 107, 215, 54, 0, 217, 127, 52, 236, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}