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: 24be8e50b54ebe6f5732a96f8dfd09b2d8a7e6eb8c2534bc55187edf6e9ac19e
Tx prefix hash: d7d604b0a5896fe215bbd0c278d6d44b58a6837be5f247f6e7a866f165741858
Tx public key: 0abd87b2afa34f5af220954b8ecc644df12f99bcc6878b3f3b7d9e74f331dbe5
| Timestamp: 1780384329 | Timestamp [UTC]: 2026-06-02 07:12:09 | Age [y:d:h:m:s]: 00:006:18:23:48 |
| Block: 5170 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2716 | RingCT/type: yes/0 |
| Extra: 010abd87b2afa34f5af220954b8ecc644df12f99bcc6878b3f3b7d9e74f331dbe502090000000326697be300 | ||
1 output(s) for total of 34.839190425446 HMNY
| stealth address | amount | amount idx | tag |
| 00: dc90f80180e80c5106d721604c4f7a42d04ea8ab046ab58026fda417579f245d | 34.839190425446 | 6549 of 0 | <b9> |
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": 5230,
"vin": [ {
"gen": {
"height": 5170
}
}
],
"vout": [ {
"amount": 34839190425446,
"target": {
"tagged_key": {
"key": "dc90f80180e80c5106d721604c4f7a42d04ea8ab046ab58026fda417579f245d",
"view_tag": "b9"
}
}
}
],
"extra": [ 1, 10, 189, 135, 178, 175, 163, 79, 90, 242, 32, 149, 75, 142, 204, 100, 77, 241, 47, 153, 188, 198, 135, 139, 63, 59, 125, 158, 116, 243, 49, 219, 229, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}