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: e78111a1588c6f46e42ca7041ba5741b818ed6a2b9b3479b963cc6bc340ae601
Tx prefix hash: e91f93b408114a4b89bc260ee9c6b99c70a2ab65fb5ffd73f4c68492c1d2ad2d
Tx public key: 01ebd2971d7aaf7423e79b8dce91c02162c3cdf4ae95297d09c5b03a2b967d65
| Timestamp: 1779972785 | Timestamp [UTC]: 2026-05-28 12:53:05 | Age [y:d:h:m:s]: 00:011:12:42:52 |
| Block: 3861 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4025 | RingCT/type: yes/0 |
| Extra: 0101ebd2971d7aaf7423e79b8dce91c02162c3cdf4ae95297d09c5b03a2b967d6502090000000226697be300 | ||
1 output(s) for total of 34.926282867189 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3d6993c20e5fc4b78db6c42c9e784951e5bb085cc07e613be5c8dec39ee303c7 | 34.926282867189 | 4718 of 0 | <b6> |
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": 3921,
"vin": [ {
"gen": {
"height": 3861
}
}
],
"vout": [ {
"amount": 34926282867189,
"target": {
"tagged_key": {
"key": "3d6993c20e5fc4b78db6c42c9e784951e5bb085cc07e613be5c8dec39ee303c7",
"view_tag": "b6"
}
}
}
],
"extra": [ 1, 1, 235, 210, 151, 29, 122, 175, 116, 35, 231, 155, 141, 206, 145, 192, 33, 98, 195, 205, 244, 174, 149, 41, 125, 9, 197, 176, 58, 43, 150, 125, 101, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}