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: c31c661a7e8b7ad29131e449cf7ceac5dc4b299adbec09158719bcf347c91d19
Tx prefix hash: fdd3a32313755c899d9b42f86a9d614df3203a5f4313f94e504c70e3a0e75a84
Tx public key: 4e6be1f30b105585a3c5a85d42a1f884ad2d63ee43ab5c92e1511607e05c5a3e
| Timestamp: 1779717770 | Timestamp [UTC]: 2026-05-25 14:02:50 | Age [y:d:h:m:s]: 00:014:12:37:46 |
| Block: 1693 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6204 | RingCT/type: yes/0 |
| Extra: 014e6be1f30b105585a3c5a85d42a1f884ad2d63ee43ab5c92e1511607e05c5a3e020900000002ba6d17be00 | ||
1 output(s) for total of 35.071006809471 HMNY
| stealth address | amount | amount idx | tag |
| 00: e0f6c78c8e3bea61a9b5a04329038c4fb3b66326b7d05ce5550eee0eef19381f | 35.071006809471 | 1862 of 0 | <7c> |
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": 1753,
"vin": [ {
"gen": {
"height": 1693
}
}
],
"vout": [ {
"amount": 35071006809471,
"target": {
"tagged_key": {
"key": "e0f6c78c8e3bea61a9b5a04329038c4fb3b66326b7d05ce5550eee0eef19381f",
"view_tag": "7c"
}
}
}
],
"extra": [ 1, 78, 107, 225, 243, 11, 16, 85, 133, 163, 197, 168, 93, 66, 161, 248, 132, 173, 45, 99, 238, 67, 171, 92, 146, 225, 81, 22, 7, 224, 92, 90, 62, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}