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: 08ed3c7dfc2e8a63bfa094ebc34370219c5fda80a45f641e87ba9ab194100706
Tx prefix hash: 3354aab0c4c9941802546e51125cde827c77b3e77bbddf9e065cb8a84f6320e3
Tx public key: 5f9abdf16de908ac56346241abc1ffd522c0ad6285e61b0cd84577c5828e75fb
| Timestamp: 1780087605 | Timestamp [UTC]: 2026-05-29 20:46:45 | Age [y:d:h:m:s]: 00:010:20:22:18 |
| Block: 4824 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3911 | RingCT/type: yes/0 |
| Extra: 015f9abdf16de908ac56346241abc1ffd522c0ad6285e61b0cd84577c5828e75fb02090000000226697be300 | ||
1 output(s) for total of 34.862189902564 HMNY
| stealth address | amount | amount idx | tag |
| 00: ccc3c63258d58db10408f3300fd351b761ba8c99ec2503bedfc3cb71fb0bf5fe | 34.862189902564 | 6070 of 0 | <c1> |
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": 4884,
"vin": [ {
"gen": {
"height": 4824
}
}
],
"vout": [ {
"amount": 34862189902564,
"target": {
"tagged_key": {
"key": "ccc3c63258d58db10408f3300fd351b761ba8c99ec2503bedfc3cb71fb0bf5fe",
"view_tag": "c1"
}
}
}
],
"extra": [ 1, 95, 154, 189, 241, 109, 233, 8, 172, 86, 52, 98, 65, 171, 193, 255, 213, 34, 192, 173, 98, 133, 230, 27, 12, 216, 69, 119, 197, 130, 142, 117, 251, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}