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: e9aa921f27e6f66c9d6bebfa99ed2fec357f98ab36914711eec692badf676270
Tx prefix hash: 4679d46582d237eedf61389d09b64648657d4618f72fb2d1d3cb064fc1f6b80f
Tx public key: f5c69a53c1b6f5a59f8d0f0ab9b7d0a1517396b88c0706aa18424cc5fe647a44
| Timestamp: 1779714118 | Timestamp [UTC]: 2026-05-25 13:01:58 | Age [y:d:h:m:s]: 00:014:11:44:49 |
| Block: 1611 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6275 | RingCT/type: yes/0 |
| Extra: 01f5c69a53c1b6f5a59f8d0f0ab9b7d0a1517396b88c0706aa18424cc5fe647a44020900000002ba6d17be00 | ||
1 output(s) for total of 35.076492439900 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7f515c4679d4b8ffb51dad809a5ad3d5aa27cbc1cb200d7586436cc83c544728 | 35.076492439900 | 1769 of 0 | <15> |
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": 1671,
"vin": [ {
"gen": {
"height": 1611
}
}
],
"vout": [ {
"amount": 35076492439900,
"target": {
"tagged_key": {
"key": "7f515c4679d4b8ffb51dad809a5ad3d5aa27cbc1cb200d7586436cc83c544728",
"view_tag": "15"
}
}
}
],
"extra": [ 1, 245, 198, 154, 83, 193, 182, 245, 165, 159, 141, 15, 10, 185, 183, 208, 161, 81, 115, 150, 184, 140, 7, 6, 170, 24, 66, 76, 197, 254, 100, 122, 68, 2, 9, 0, 0, 0, 2, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}