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: 2bea107c1d015117303b94bf8537878ba6a86d033945f1f2ee2bb0395375323e
Tx prefix hash: 290be23cdd77f096d6af81720d833f36a2935ce07b630e42ea5257ac6123b209
Tx public key: f1084393d983a92d9d580798f2bd96f9226ded56d6d623691e814bc03c269c41
| Timestamp: 1780694308 | Timestamp [UTC]: 2026-06-05 21:18:28 | Age [y:d:h:m:s]: 00:003:05:22:08 |
| Block: 5928 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1969 | RingCT/type: yes/0 |
| Extra: 01f1084393d983a92d9d580798f2bd96f9226ded56d6d623691e814bc03c269c41020900000001e49593ff00 | ||
1 output(s) for total of 34.788857305749 HMNY
| stealth address | amount | amount idx | tag |
| 00: d61a71856a7b36276b38b97a8bd4eb12edda29a07cc525bacdeb30d98f0f8a0a | 34.788857305749 | 7389 of 0 | <c5> |
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": 5988,
"vin": [ {
"gen": {
"height": 5928
}
}
],
"vout": [ {
"amount": 34788857305749,
"target": {
"tagged_key": {
"key": "d61a71856a7b36276b38b97a8bd4eb12edda29a07cc525bacdeb30d98f0f8a0a",
"view_tag": "c5"
}
}
}
],
"extra": [ 1, 241, 8, 67, 147, 217, 131, 169, 45, 157, 88, 7, 152, 242, 189, 150, 249, 34, 109, 237, 86, 214, 214, 35, 105, 30, 129, 75, 192, 60, 38, 156, 65, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}