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: d0f66f3f512093e60b7ba770b667682a5da454f4c35551c070823316d6a36cb0
Tx prefix hash: e50fcf0dac49cccdc190a43041cedbe853b4524b5ba4de6137ff82850eb24df7
Tx public key: a4b5c3593c1aa669dc459ed82ec15e588e0d050899cb145f6f8acebffad3e6ae
| Timestamp: 1780025228 | Timestamp [UTC]: 2026-05-29 03:27:08 | Age [y:d:h:m:s]: 00:010:22:08:49 |
| Block: 4167 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3719 | RingCT/type: yes/0 |
| Extra: 01a4b5c3593c1aa669dc459ed82ec15e588e0d050899cb145f6f8acebffad3e6ae02090000000a26697be300 | ||
1 output(s) for total of 34.905904116399 HMNY
| stealth address | amount | amount idx | tag |
| 00: 79ae42fb5559797548258749e6729fa84a0c17c456105c4dcc994db3dc3cc4a2 | 34.905904116399 | 5200 of 0 | <8d> |
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": 4227,
"vin": [ {
"gen": {
"height": 4167
}
}
],
"vout": [ {
"amount": 34905904116399,
"target": {
"tagged_key": {
"key": "79ae42fb5559797548258749e6729fa84a0c17c456105c4dcc994db3dc3cc4a2",
"view_tag": "8d"
}
}
}
],
"extra": [ 1, 164, 181, 195, 89, 60, 26, 166, 105, 220, 69, 158, 216, 46, 193, 94, 88, 142, 13, 5, 8, 153, 203, 20, 95, 111, 138, 206, 191, 250, 211, 230, 174, 2, 9, 0, 0, 0, 10, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}