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: 1c5e8016869f29a1a502b386c94e8b989bc2f4d1c25f7206661c035068e605a0
Tx prefix hash: 1a1ae611b9bdcc1257b6a2e01d829d3f86c09dc669f418a4a26c984a27b54e6c
Tx public key: 2810636e3dc08d824086a031ca0ee7667d3b69ed4506c75ac226eb29ab032f71
| Timestamp: 1779629330 | Timestamp [UTC]: 2026-05-24 13:28:50 | Age [y:d:h:m:s]: 00:015:12:07:07 |
| Block: 825 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7061 | RingCT/type: yes/0 |
| Extra: 012810636e3dc08d824086a031ca0ee7667d3b69ed4506c75ac226eb29ab032f71020900000001ba6d17be00 | ||
1 output(s) for total of 35.129117764064 HMNY
| stealth address | amount | amount idx | tag |
| 00: 62d0e89400fd6c2ef20f3a9704d0cbe44af6c7520f96c59dd6b9122655b5de9d | 35.129117764064 | 957 of 0 | <00> |
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": 885,
"vin": [ {
"gen": {
"height": 825
}
}
],
"vout": [ {
"amount": 35129117764064,
"target": {
"tagged_key": {
"key": "62d0e89400fd6c2ef20f3a9704d0cbe44af6c7520f96c59dd6b9122655b5de9d",
"view_tag": "00"
}
}
}
],
"extra": [ 1, 40, 16, 99, 110, 61, 192, 141, 130, 64, 134, 160, 49, 202, 14, 231, 102, 125, 59, 105, 237, 69, 6, 199, 90, 194, 38, 235, 41, 171, 3, 47, 113, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}