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: 82865dac9e2af2890b4d7a8b6dc958d4f6cc53de43b5140791230729282a4e86
Tx prefix hash: f2500f9ef314dc7cc3603b87200e7bdbd8f1e073bfe25283a7e5a659ddc343c1
Tx public key: 9a6b2e18e3c861c0ead1c5ff77286d5dbfa5cb954a924d9ff7895a89a3440c63
| Timestamp: 1779637477 | Timestamp [UTC]: 2026-05-24 15:44:37 | Age [y:d:h:m:s]: 00:019:19:17:39 |
| Block: 1158 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7587 | RingCT/type: yes/0 |
| Extra: 019a6b2e18e3c861c0ead1c5ff77286d5dbfa5cb954a924d9ff7895a89a3440c63020900000001ba6d17be00 | ||
1 output(s) for total of 35.106812669961 HMNY
| stealth address | amount | amount idx | tag |
| 00: 439c0b0e84896985569a76adcd3b6ef3ed79a03ceeaa948201424e926956d5b1 | 35.106812669961 | 1300 of 0 | <00> |
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": 1218,
"vin": [ {
"gen": {
"height": 1158
}
}
],
"vout": [ {
"amount": 35106812669961,
"target": {
"tagged_key": {
"key": "439c0b0e84896985569a76adcd3b6ef3ed79a03ceeaa948201424e926956d5b1",
"view_tag": "00"
}
}
}
],
"extra": [ 1, 154, 107, 46, 24, 227, 200, 97, 192, 234, 209, 197, 255, 119, 40, 109, 93, 191, 165, 203, 149, 74, 146, 77, 159, 247, 137, 90, 137, 163, 68, 12, 99, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}