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: 64839ba17972e5f3f8c079fe9b65f94e94b591ee60cfaf4e7ca5c469d3ab09e5
Tx prefix hash: 92de9ee14375633bff326ce18dcb6ebe193b986ec7e1e2ae7b86d9a0c1b78330
Tx public key: ce6c84b017a6ce402c86b359c6decf85a40e71c4b7a4e272b8e19c3dda455915
| Timestamp: 1780018835 | Timestamp [UTC]: 2026-05-29 01:40:35 | Age [y:d:h:m:s]: 00:011:01:00:01 |
| Block: 4131 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3765 | RingCT/type: yes/0 |
| Extra: 01ce6c84b017a6ce402c86b359c6decf85a40e71c4b7a4e272b8e19c3dda45591502090000000526697be300 | ||
1 output(s) for total of 34.910914599200 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1e341b98e664510bc84055cb0126a84a6e1c67ec3cf4773ffce84ec781282e09 | 34.910914599200 | 5158 of 0 | <2f> |
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": 4191,
"vin": [ {
"gen": {
"height": 4131
}
}
],
"vout": [ {
"amount": 34910914599200,
"target": {
"tagged_key": {
"key": "1e341b98e664510bc84055cb0126a84a6e1c67ec3cf4773ffce84ec781282e09",
"view_tag": "2f"
}
}
}
],
"extra": [ 1, 206, 108, 132, 176, 23, 166, 206, 64, 44, 134, 179, 89, 198, 222, 207, 133, 164, 14, 113, 196, 183, 164, 226, 114, 184, 225, 156, 61, 218, 69, 89, 21, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}