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: e0937755c32b27cfba920404e5871e2bcbb3806bab5729db3f9d7ad94151cab6
Tx prefix hash: 8c4079768100e467aa5ae08acc809b81eff41b042984f69308dea6bc90d1e2d5
Tx public key: 88dcd76316d928b9539f8d2f3778d055bd7c9f23d7e652a5f4f1e3104d5da1b8
| Timestamp: 1780083652 | Timestamp [UTC]: 2026-05-29 19:40:52 | Age [y:d:h:m:s]: 00:010:05:05:55 |
| Block: 4789 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3097 | RingCT/type: yes/0 |
| Extra: 0188dcd76316d928b9539f8d2f3778d055bd7c9f23d7e652a5f4f1e3104d5da1b802090000000226697be300 | ||
1 output(s) for total of 34.864517284726 HMNY
| stealth address | amount | amount idx | tag |
| 00: 49e2b9490cc770ffdb1c9bd0d9ee3fdb0552aed057578839d12494590071a4d4 | 34.864517284726 | 6022 of 0 | <b1> |
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": 4849,
"vin": [ {
"gen": {
"height": 4789
}
}
],
"vout": [ {
"amount": 34864517284726,
"target": {
"tagged_key": {
"key": "49e2b9490cc770ffdb1c9bd0d9ee3fdb0552aed057578839d12494590071a4d4",
"view_tag": "b1"
}
}
}
],
"extra": [ 1, 136, 220, 215, 99, 22, 217, 40, 185, 83, 159, 141, 47, 55, 120, 208, 85, 189, 124, 159, 35, 215, 230, 82, 165, 244, 241, 227, 16, 77, 93, 161, 184, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}