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: b80738461a7a39c788bb8c0e965451fc22698753b9a6194a34aa060dde63dd36
Tx prefix hash: 028c4df75707d703847bccd7b64baf74f95b0926cf878c59247f5e5a0ea888fe
Tx public key: 45b38be1880b14041d408ed81d8f2a71ecf21d75d7094e8bf404b08c53ff1b42
| Timestamp: 1780777988 | Timestamp [UTC]: 2026-06-06 20:33:08 | Age [y:d:h:m:s]: 00:002:02:45:45 |
| Block: 6740 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1146 | RingCT/type: yes/0 |
| Extra: 0145b38be1880b14041d408ed81d8f2a71ecf21d75d7094e8bf404b08c53ff1b42020900000004e49593ff00 | ||
1 output(s) for total of 34.739237119284 HMNY
| stealth address | amount | amount idx | tag |
| 00: bb433f8bfcd9f90e10714438d30f2a35831d02a2bf7e91e7ae272ccd69cbdd84 | 34.739237119284 | 8314 of 0 | <0c> |
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": 6800,
"vin": [ {
"gen": {
"height": 6740
}
}
],
"vout": [ {
"amount": 34739237119284,
"target": {
"tagged_key": {
"key": "bb433f8bfcd9f90e10714438d30f2a35831d02a2bf7e91e7ae272ccd69cbdd84",
"view_tag": "0c"
}
}
}
],
"extra": [ 1, 69, 179, 139, 225, 136, 11, 20, 4, 29, 64, 142, 216, 29, 143, 42, 113, 236, 242, 29, 117, 215, 9, 78, 139, 244, 4, 176, 140, 83, 255, 27, 66, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}