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: 1690d12551d78c732313011b2068886f6f6567fda3b1888ff26b662eb6b49f10
Tx prefix hash: 79a2ff26061ea04ad21bc640698b85bbbaf6c8795054c5d09d6e4883cc2c11a6
Tx public key: 46a1710ab445e9a36a85cda41e2385806ffc42b029a2415edf9ae50d0bd07dc3
| Timestamp: 1779842597 | Timestamp [UTC]: 2026-05-27 00:43:17 | Age [y:d:h:m:s]: 00:012:22:35:36 |
| Block: 2411 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5475 | RingCT/type: yes/0 |
| Extra: 0146a1710ab445e9a36a85cda41e2385806ffc42b029a2415edf9ae50d0bd07dc302090000000326697be300 | ||
1 output(s) for total of 35.023010722665 HMNY
| stealth address | amount | amount idx | tag |
| 00: f11c607fb76b2ef977e1aabcf351f6a4efaad58f319bbffdea01e90c3e4070ef | 35.023010722665 | 2831 of 0 | <c4> |
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": 2471,
"vin": [ {
"gen": {
"height": 2411
}
}
],
"vout": [ {
"amount": 35023010722665,
"target": {
"tagged_key": {
"key": "f11c607fb76b2ef977e1aabcf351f6a4efaad58f319bbffdea01e90c3e4070ef",
"view_tag": "c4"
}
}
}
],
"extra": [ 1, 70, 161, 113, 10, 180, 69, 233, 163, 106, 133, 205, 164, 30, 35, 133, 128, 111, 252, 66, 176, 41, 162, 65, 94, 223, 154, 229, 13, 11, 208, 125, 195, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}