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: 91abea5f45b36a0456028bcaad0cb2746dce63b284688d227a9facde06daea04
Tx prefix hash: e8d63b78db62d085ae6e3c3192d5a07f4b8dfce60cf7ad5bdd16753c7ef0fd6c
Tx public key: 3fbcb29f473958ea0df89dcf97c91a100000fce49a0ac771056593b05f5c9f26
| Timestamp: 1779722307 | Timestamp [UTC]: 2026-05-25 15:18:27 | Age [y:d:h:m:s]: 00:014:12:20:23 |
| Block: 1775 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6170 | RingCT/type: yes/0 |
| Extra: 013fbcb29f473958ea0df89dcf97c91a100000fce49a0ac771056593b05f5c9f26020900000003ba6d17be00 | ||
1 output(s) for total of 35.065522036943 HMNY
| stealth address | amount | amount idx | tag |
| 00: 776f0dde137bf4b254bd3f8936c9f78585328e7c2752c93199af3768aff2bc5a | 35.065522036943 | 1960 of 0 | <e5> |
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": 1835,
"vin": [ {
"gen": {
"height": 1775
}
}
],
"vout": [ {
"amount": 35065522036943,
"target": {
"tagged_key": {
"key": "776f0dde137bf4b254bd3f8936c9f78585328e7c2752c93199af3768aff2bc5a",
"view_tag": "e5"
}
}
}
],
"extra": [ 1, 63, 188, 178, 159, 71, 57, 88, 234, 13, 248, 157, 207, 151, 201, 26, 16, 0, 0, 252, 228, 154, 10, 199, 113, 5, 101, 147, 176, 95, 92, 159, 38, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}