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: db9aa1e0b3c16f9346a5adbb700aeaa52895f601e29eab14524b956fc9dc3950
Tx prefix hash: e7088e58e80b09fdc7578984ac445d2192b9f19b0ca55553255d7b5a324a9786
Tx public key: 9a6785c96d122cb28ec457320e4c0e151c4b9a68fa9a5ca5d07d67f2a5ff4613
| Timestamp: 1780323448 | Timestamp [UTC]: 2026-06-01 14:17:28 | Age [y:d:h:m:s]: 00:007:11:18:29 |
| Block: 5143 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2743 | RingCT/type: yes/0 |
| Extra: 019a6785c96d122cb28ec457320e4c0e151c4b9a68fa9a5ca5d07d67f2a5ff461302090000005626697be300 | ||
1 output(s) for total of 34.840984636377 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4262b20301103e46b6a3d220e835760d613d4b45d9a4e92e634d4f9fec2afe98 | 34.840984636377 | 6518 of 0 | <fb> |
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": 5203,
"vin": [ {
"gen": {
"height": 5143
}
}
],
"vout": [ {
"amount": 34840984636377,
"target": {
"tagged_key": {
"key": "4262b20301103e46b6a3d220e835760d613d4b45d9a4e92e634d4f9fec2afe98",
"view_tag": "fb"
}
}
}
],
"extra": [ 1, 154, 103, 133, 201, 109, 18, 44, 178, 142, 196, 87, 50, 14, 76, 14, 21, 28, 75, 154, 104, 250, 154, 92, 165, 208, 125, 103, 242, 165, 255, 70, 19, 2, 9, 0, 0, 0, 86, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}