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: 3ae1209694e1ac90de0af34528ab3af6ef8bcd51ebbd7249be487e46585540ce
Tx prefix hash: f067c4de7bb6cfdfb0cfef52ab7174d87be1ce5d3e7eb0d7e6fe8bc513071e0b
Tx public key: 6ca194ccb423562aebd5d3148c7ac83a665c6565a5c978d2dcc265ccf115ee14
| Timestamp: 1779636241 | Timestamp [UTC]: 2026-05-24 15:24:01 | Age [y:d:h:m:s]: 00:015:11:25:47 |
| Block: 1100 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6820 | RingCT/type: yes/0 |
| Extra: 016ca194ccb423562aebd5d3148c7ac83a665c6565a5c978d2dcc265ccf115ee14020900000002ba6d17be00 | ||
1 output(s) for total of 35.110696622502 HMNY
| stealth address | amount | amount idx | tag |
| 00: 46b7263771277a91876a78c85096865b4eafbee61b88a3522e90538745370fe6 | 35.110696622502 | 1240 of 0 | <8a> |
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": 1160,
"vin": [ {
"gen": {
"height": 1100
}
}
],
"vout": [ {
"amount": 35110696622502,
"target": {
"tagged_key": {
"key": "46b7263771277a91876a78c85096865b4eafbee61b88a3522e90538745370fe6",
"view_tag": "8a"
}
}
}
],
"extra": [ 1, 108, 161, 148, 204, 180, 35, 86, 42, 235, 213, 211, 20, 140, 122, 200, 58, 102, 92, 101, 101, 165, 201, 120, 210, 220, 194, 101, 204, 241, 21, 238, 20, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}