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: ebeed8449676dce6547097c9d0eef8e75bfe7966a58d4d3242a282a24e887562
Tx prefix hash: 129fae4178ecacd2e0aefee0a77197d44c985a9839f2ed7ca939ba79cedc549c
Tx public key: 0a2f71e6b5913448098ca64fe9eb8e7d9b734d58f183e47be35d8d482d754c7b
| Timestamp: 1779630336 | Timestamp [UTC]: 2026-05-24 13:45:36 | Age [y:d:h:m:s]: 00:015:11:50:21 |
| Block: 868 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7018 | RingCT/type: yes/0 |
| Extra: 010a2f71e6b5913448098ca64fe9eb8e7d9b734d58f183e47be35d8d482d754c7b020900000002ba6d17be00 | ||
1 output(s) for total of 35.126236730049 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9424d9ed6e70ddd682dafeae99cfc5e4f4d40ccf7b106e665f018a74607e69ad | 35.126236730049 | 1000 of 0 | <87> |
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": 928,
"vin": [ {
"gen": {
"height": 868
}
}
],
"vout": [ {
"amount": 35126236730049,
"target": {
"tagged_key": {
"key": "9424d9ed6e70ddd682dafeae99cfc5e4f4d40ccf7b106e665f018a74607e69ad",
"view_tag": "87"
}
}
}
],
"extra": [ 1, 10, 47, 113, 230, 181, 145, 52, 72, 9, 140, 166, 79, 233, 235, 142, 125, 155, 115, 77, 88, 241, 131, 228, 123, 227, 93, 141, 72, 45, 117, 76, 123, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}