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: 328918f322889e398fa6c02fff1b3b1455df8aff2a280308b14ef100b4236ed1
Tx prefix hash: bd85795ed10230bc30c31acbd7210d0e30d81a1d515eebdbd9f71c2cc6cbeb87
Tx public key: 0e0aeb7eb8552922555a15ee823df26faff6f7702e82fc8e9a23cef5d850afb3
| Timestamp: 1780323383 | Timestamp [UTC]: 2026-06-01 14:16:23 | Age [y:d:h:m:s]: 00:007:10:30:24 |
| Block: 5124 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2762 | RingCT/type: yes/0 |
| Extra: 010e0aeb7eb8552922555a15ee823df26faff6f7702e82fc8e9a23cef5d850afb302090000002726697be300 | ||
1 output(s) for total of 34.842247284643 HMNY
| stealth address | amount | amount idx | tag |
| 00: d767fd45779a6e9d48fe0b6c06c24ddbf388e8126985fc62b10a388d63114c56 | 34.842247284643 | 6499 of 0 | <9f> |
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": 5184,
"vin": [ {
"gen": {
"height": 5124
}
}
],
"vout": [ {
"amount": 34842247284643,
"target": {
"tagged_key": {
"key": "d767fd45779a6e9d48fe0b6c06c24ddbf388e8126985fc62b10a388d63114c56",
"view_tag": "9f"
}
}
}
],
"extra": [ 1, 14, 10, 235, 126, 184, 85, 41, 34, 85, 90, 21, 238, 130, 61, 242, 111, 175, 246, 247, 112, 46, 130, 252, 142, 154, 35, 206, 245, 216, 80, 175, 179, 2, 9, 0, 0, 0, 39, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}