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: e94e537fa36985274d573e4c89c701d9a58b4a4252108619fde587109c075265
Tx prefix hash: 556502ac17bc0a9d6069d850042631688048470115f06aeabb2f6191be815a27
Tx public key: 145c77c641d1b9e7fd167a8d4135375a9ebbdefc29f0ce54b981fcd1764f022c
| Timestamp: 1780696811 | Timestamp [UTC]: 2026-06-05 22:00:11 | Age [y:d:h:m:s]: 00:003:04:49:37 |
| Block: 6000 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1900 | RingCT/type: yes/0 |
| Extra: 01145c77c641d1b9e7fd167a8d4135375a9ebbdefc29f0ce54b981fcd1764f022c020900000002e49593ff00 | ||
1 output(s) for total of 34.810720106706 HMNY
| stealth address | amount | amount idx | tag |
| 00: f9379c16a0ed2731266f3d42a6da2b6c8dc8b8d3eaa900a017a020826b921a18 | 34.810720106706 | 7465 of 0 | <54> |
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": 6060,
"vin": [ {
"gen": {
"height": 6000
}
}
],
"vout": [ {
"amount": 34810720106706,
"target": {
"tagged_key": {
"key": "f9379c16a0ed2731266f3d42a6da2b6c8dc8b8d3eaa900a017a020826b921a18",
"view_tag": "54"
}
}
}
],
"extra": [ 1, 20, 92, 119, 198, 65, 209, 185, 231, 253, 22, 122, 141, 65, 53, 55, 90, 158, 187, 222, 252, 41, 240, 206, 84, 185, 129, 252, 209, 118, 79, 2, 44, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}