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: 553f1925ca7d079fc071e462f5173e62068e9f944cfef66db5a37dddf1082dce
Tx prefix hash: 7b1d8f682d3093782a36461143217996aae8e95b1d3501b83aded3dd445eec8f
Tx public key: e6d567ca4b0ae9a154263fa7acbf15e42671ca41c7d6fb216add50729040ea86
| Timestamp: 1780075587 | Timestamp [UTC]: 2026-05-29 17:26:27 | Age [y:d:h:m:s]: 00:010:08:09:30 |
| Block: 4698 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3188 | RingCT/type: yes/0 |
| Extra: 01e6d567ca4b0ae9a154263fa7acbf15e42671ca41c7d6fb216add50729040ea8602090000000326697be300 | ||
1 output(s) for total of 34.870569205527 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0f5c5900252befc0a13f3fa0632a91df24cf4282bc36abeb294562da7246d419 | 34.870569205527 | 5902 of 0 | <46> |
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": 4758,
"vin": [ {
"gen": {
"height": 4698
}
}
],
"vout": [ {
"amount": 34870569205527,
"target": {
"tagged_key": {
"key": "0f5c5900252befc0a13f3fa0632a91df24cf4282bc36abeb294562da7246d419",
"view_tag": "46"
}
}
}
],
"extra": [ 1, 230, 213, 103, 202, 75, 10, 233, 161, 84, 38, 63, 167, 172, 191, 21, 228, 38, 113, 202, 65, 199, 214, 251, 33, 106, 221, 80, 114, 144, 64, 234, 134, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}