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: ef8473de47e43a66893f0ba6d93184a7ff5a59e78f4998328842d18501049fe4
Tx prefix hash: 39f8be66818e150c6a4e0543cc7044558086553b72a7b1b292faa5d5cb3a4944
Tx public key: 14481264336ce1b1fde7e5af5c5f185daf99a5bf6267b815d17f4c762686f9b9
| Timestamp: 1779634773 | Timestamp [UTC]: 2026-05-24 14:59:33 | Age [y:d:h:m:s]: 00:015:11:50:15 |
| Block: 1046 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6854 | RingCT/type: yes/0 |
| Extra: 0114481264336ce1b1fde7e5af5c5f185daf99a5bf6267b815d17f4c762686f9b9020900000002ba6d17be00 | ||
1 output(s) for total of 35.114313102507 HMNY
| stealth address | amount | amount idx | tag |
| 00: 642de048f7e4aff177c37f048ce437e740e0166480870b178139550827607eeb | 35.114313102507 | 1184 of 0 | <be> |
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": 1106,
"vin": [ {
"gen": {
"height": 1046
}
}
],
"vout": [ {
"amount": 35114313102507,
"target": {
"tagged_key": {
"key": "642de048f7e4aff177c37f048ce437e740e0166480870b178139550827607eeb",
"view_tag": "be"
}
}
}
],
"extra": [ 1, 20, 72, 18, 100, 51, 108, 225, 177, 253, 231, 229, 175, 92, 95, 24, 93, 175, 153, 165, 191, 98, 103, 184, 21, 209, 127, 76, 118, 38, 134, 249, 185, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}