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: a92587974d947de3895f3f8818181407d255b6c4d40e9dd9bb6d9f8c9ad6807a
Tx prefix hash: ae03a11d06abc5b94818658fe4526c3003a4dfd0380212578e41480a2b675d97
Tx public key: a1ff97fd67dddb4e9bf6dc037fefd686667475002266f60df51c87055f00679a
| Timestamp: 1780814807 | Timestamp [UTC]: 2026-06-07 06:46:47 | Age [y:d:h:m:s]: 00:001:16:32:06 |
| Block: 7045 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 841 | RingCT/type: yes/0 |
| Extra: 01a1ff97fd67dddb4e9bf6dc037fefd686667475002266f60df51c87055f00679a020900000001e49593ff00 | ||
1 output(s) for total of 34.714818180124 HMNY
| stealth address | amount | amount idx | tag |
| 00: 145b31a3ee85aff1cc1f8c49a9f005089ae3deb81ff588bc33a50ccffbe5e67b | 34.714818180124 | 8687 of 0 | <16> |
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": 7105,
"vin": [ {
"gen": {
"height": 7045
}
}
],
"vout": [ {
"amount": 34714818180124,
"target": {
"tagged_key": {
"key": "145b31a3ee85aff1cc1f8c49a9f005089ae3deb81ff588bc33a50ccffbe5e67b",
"view_tag": "16"
}
}
}
],
"extra": [ 1, 161, 255, 151, 253, 103, 221, 219, 78, 155, 246, 220, 3, 127, 239, 214, 134, 102, 116, 117, 0, 34, 102, 246, 13, 245, 28, 135, 5, 95, 0, 103, 154, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}