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: a389424b8a45a20570cc44533e5feaedd293c603a42814a72c67d3a2c96ea32e
Tx prefix hash: f0c82ae67cf24ff4f5fb0fe346b2a78a1cc3e1b42d0f907c11de92b3f56b2548
Tx public key: 72731e13ed9fd8df4388472e2f80c096cf2e877f7cc9d89a9f665bb8f17beca5
| Timestamp: 1779636358 | Timestamp [UTC]: 2026-05-24 15:25:58 | Age [y:d:h:m:s]: 00:023:16:56:21 |
| Block: 1110 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7635 | RingCT/type: yes/0 |
| Extra: 0172731e13ed9fd8df4388472e2f80c096cf2e877f7cc9d89a9f665bb8f17beca5020900000001ba6d17be00 | ||
1 output(s) for total of 35.110026944857 HMNY
| stealth address | amount | amount idx | tag |
| 00: f3950e7f46684841026fa430c22d731448e0ca88bd239f8d3008112b1de7ed94 | 35.110026944857 | 1250 of 0 | <e3> |
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": 1170,
"vin": [ {
"gen": {
"height": 1110
}
}
],
"vout": [ {
"amount": 35110026944857,
"target": {
"tagged_key": {
"key": "f3950e7f46684841026fa430c22d731448e0ca88bd239f8d3008112b1de7ed94",
"view_tag": "e3"
}
}
}
],
"extra": [ 1, 114, 115, 30, 19, 237, 159, 216, 223, 67, 136, 71, 46, 47, 128, 192, 150, 207, 46, 135, 127, 124, 201, 216, 154, 159, 102, 91, 184, 241, 123, 236, 165, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}