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: 147a2582d8df7428f946ef9211800e2f310290024dddccdfb308d5e090afe6f3
Tx prefix hash: 2e9e87adacc808d1ac06272f3eb63a8b31535d35d96cadf067e9fb3bf466f12b
Tx public key: 7a3e98dbe9d2b4d948a2fff74810db43aa8c684674fb078ab2647c9f02980587
| Timestamp: 1780008307 | Timestamp [UTC]: 2026-05-28 22:45:07 | Age [y:d:h:m:s]: 00:011:04:04:41 |
| Block: 4088 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3832 | RingCT/type: yes/0 |
| Extra: 017a3e98dbe9d2b4d948a2fff74810db43aa8c684674fb078ab2647c9f0298058702090000000326697be300 | ||
1 output(s) for total of 34.911164158249 HMNY
| stealth address | amount | amount idx | tag |
| 00: 68024d6521a9a2adacdef10bafd95d24a01edcc305d4d7991023c9e6468d9436 | 34.911164158249 | 5080 of 0 | <05> |
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": 4148,
"vin": [ {
"gen": {
"height": 4088
}
}
],
"vout": [ {
"amount": 34911164158249,
"target": {
"tagged_key": {
"key": "68024d6521a9a2adacdef10bafd95d24a01edcc305d4d7991023c9e6468d9436",
"view_tag": "05"
}
}
}
],
"extra": [ 1, 122, 62, 152, 219, 233, 210, 180, 217, 72, 162, 255, 247, 72, 16, 219, 67, 170, 140, 104, 70, 116, 251, 7, 138, 178, 100, 124, 159, 2, 152, 5, 135, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}