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: 7d2d57fbc33ce36dab1ed74e4188be21549ce38f6cc82334abfce12bb954df67
Tx prefix hash: 5237f38fb8c72ec35299c5c8f7589be0cf9fa8b752d7149628342a4a03707e18
Tx public key: f9e52750ee85d37259d4603b2b93d98d543018c6827db10e99d47c1ef55efac4
| Timestamp: 1779632188 | Timestamp [UTC]: 2026-05-24 14:16:28 | Age [y:d:h:m:s]: 00:015:11:19:29 |
| Block: 942 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6944 | RingCT/type: yes/0 |
| Extra: 01f9e52750ee85d37259d4603b2b93d98d543018c6827db10e99d47c1ef55efac4020900000002ba6d17be00 | ||
1 output(s) for total of 35.121279224700 HMNY
| stealth address | amount | amount idx | tag |
| 00: 96d6c285ff39c6e7b26da6bf8980c80a029b18cba3a1280121161f12ddb1b2cc | 35.121279224700 | 1076 of 0 | <6d> |
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": 1002,
"vin": [ {
"gen": {
"height": 942
}
}
],
"vout": [ {
"amount": 35121279224700,
"target": {
"tagged_key": {
"key": "96d6c285ff39c6e7b26da6bf8980c80a029b18cba3a1280121161f12ddb1b2cc",
"view_tag": "6d"
}
}
}
],
"extra": [ 1, 249, 229, 39, 80, 238, 133, 211, 114, 89, 212, 96, 59, 43, 147, 217, 141, 84, 48, 24, 198, 130, 125, 177, 14, 153, 212, 124, 30, 245, 94, 250, 196, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}