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: 4afeb9006301c7deaa0f8f182869e559aa1d6f6777cccffe949f1b43ee84c8c4
Tx prefix hash: f4f27d79c8291daf49b8b6b2c3d43650ab28a5b28547f82e33e955e53d7f1ff8
Tx public key: 790ec6155f725c0f6f6d183f3ebfac4e0a1c89cb01c72dcda225bd3b37c6b228
| Timestamp: 1779772950 | Timestamp [UTC]: 2026-05-26 05:22:30 | Age [y:d:h:m:s]: 00:013:19:24:17 |
| Block: 2039 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5847 | RingCT/type: yes/0 |
| Extra: 01790ec6155f725c0f6f6d183f3ebfac4e0a1c89cb01c72dcda225bd3b37c6b22802090000000126697be300 | ||
1 output(s) for total of 35.047869570507 HMNY
| stealth address | amount | amount idx | tag |
| 00: 11de6d5d50f71c21bccdc868ca70609e5158bad69d0c43ca2be797b5008368ef | 35.047869570507 | 2331 of 0 | <4f> |
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": 2099,
"vin": [ {
"gen": {
"height": 2039
}
}
],
"vout": [ {
"amount": 35047869570507,
"target": {
"tagged_key": {
"key": "11de6d5d50f71c21bccdc868ca70609e5158bad69d0c43ca2be797b5008368ef",
"view_tag": "4f"
}
}
}
],
"extra": [ 1, 121, 14, 198, 21, 95, 114, 92, 15, 111, 109, 24, 63, 62, 191, 172, 78, 10, 28, 137, 203, 1, 199, 45, 205, 162, 37, 189, 59, 55, 198, 178, 40, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}