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: a37a367834e75e9217bd5fca4a624e41523cdaa07643b0431b68efaaefecfd20
Tx prefix hash: 103af9e9a7b6b2104bf3e7086e84354d119e88837ad3d75d2620bad2df4c70d3
Tx public key: 4f0dbf09a2b4f15d40c55fcbb559bd75291a13abd8125678316db10c6d87a9e1
| Timestamp: 1779730864 | Timestamp [UTC]: 2026-05-25 17:41:04 | Age [y:d:h:m:s]: 00:018:17:21:12 |
| Block: 1880 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6865 | RingCT/type: yes/0 |
| Extra: 014f0dbf09a2b4f15d40c55fcbb559bd75291a13abd8125678316db10c6d87a9e1020900000001ba6d17be00 | ||
1 output(s) for total of 35.061112504987 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9146d393738363d060ca1fc4eda01ec102c8c3443065608f5a6de0ab6367379a | 35.061112504987 | 2095 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": 1940,
"vin": [ {
"gen": {
"height": 1880
}
}
],
"vout": [ {
"amount": 35061112504987,
"target": {
"tagged_key": {
"key": "9146d393738363d060ca1fc4eda01ec102c8c3443065608f5a6de0ab6367379a",
"view_tag": "8a"
}
}
}
],
"extra": [ 1, 79, 13, 191, 9, 162, 180, 241, 93, 64, 197, 95, 203, 181, 89, 189, 117, 41, 26, 19, 171, 216, 18, 86, 120, 49, 109, 177, 12, 109, 135, 169, 225, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}