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: eae0c82e5b681ec2ba70e33cd3f7b32a1ffe71160aca706054f78268ea433a7c
Tx prefix hash: 7c795e250e7ae388304262bef9a0817911a50b07d258d1a0b7890dc031a8aa3d
Tx public key: ee52aa501a7527d6186766c3f3eb3d919ab44ad7c56ec4a8deb6dde4f74b38a9
| Timestamp: 1780866552 | Timestamp [UTC]: 2026-06-07 21:09:12 | Age [y:d:h:m:s]: 00:001:00:02:55 |
| Block: 7672 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 214 | RingCT/type: yes/0 |
| Extra: 01ee52aa501a7527d6186766c3f3eb3d919ab44ad7c56ec4a8deb6dde4f74b38a9020900000001e49593ff00 | ||
1 output(s) for total of 34.673327240522 HMNY
| stealth address | amount | amount idx | tag |
| 00: f018bb0a65ae016b956264f9604a99118eeadcb5788e345f39dac75ed0e23894 | 34.673327240522 | 9486 of 0 | <5d> |
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": 7732,
"vin": [ {
"gen": {
"height": 7672
}
}
],
"vout": [ {
"amount": 34673327240522,
"target": {
"tagged_key": {
"key": "f018bb0a65ae016b956264f9604a99118eeadcb5788e345f39dac75ed0e23894",
"view_tag": "5d"
}
}
}
],
"extra": [ 1, 238, 82, 170, 80, 26, 117, 39, 214, 24, 103, 102, 195, 243, 235, 61, 145, 154, 180, 74, 215, 197, 110, 196, 168, 222, 182, 221, 228, 247, 75, 56, 169, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}