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: 34319eae296d9245be09e5ca67606c8c77243e2f9f4b85abeca72c0e8610db9a
Tx prefix hash: 9a801fa18623b5d8ea748eba8b7116b03cd42256bdfe2c1518d124481e2245ed
Tx public key: 2e0973e832bedc67dcde9c15bad74f0d9f92dac776dc80b020b70e190c605442
| Timestamp: 1779717683 | Timestamp [UTC]: 2026-05-25 14:01:23 | Age [y:d:h:m:s]: 00:014:10:21:46 |
| Block: 1690 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6196 | RingCT/type: yes/0 |
| Extra: 012e0973e832bedc67dcde9c15bad74f0d9f92dac776dc80b020b70e190c605442020900000001ba6d17be00 | ||
1 output(s) for total of 35.071207488147 HMNY
| stealth address | amount | amount idx | tag |
| 00: 971a934384fec6170434fcfcfeb5411cbf1d754b603e3d9bbfdc130781233ffa | 35.071207488147 | 1859 of 0 | <7e> |
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": 1750,
"vin": [ {
"gen": {
"height": 1690
}
}
],
"vout": [ {
"amount": 35071207488147,
"target": {
"tagged_key": {
"key": "971a934384fec6170434fcfcfeb5411cbf1d754b603e3d9bbfdc130781233ffa",
"view_tag": "7e"
}
}
}
],
"extra": [ 1, 46, 9, 115, 232, 50, 190, 220, 103, 220, 222, 156, 21, 186, 215, 79, 13, 159, 146, 218, 199, 118, 220, 128, 176, 32, 183, 14, 25, 12, 96, 84, 66, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}