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: fe85bec7ffc49b8d32505708e99084078aeab029f9506fdafa73b4a654ab2019
Tx prefix hash: 4e105201b4bc2d28435fef83366c0c702a295820594ad70ebebfe9a3867c44b5
Tx public key: 7f0291f2de20934ec370a5e82bcdc4fbaf28a6dc17e5b1d97520214826e17ae4
| Timestamp: 1780755122 | Timestamp [UTC]: 2026-06-06 14:12:02 | Age [y:d:h:m:s]: 00:002:10:34:45 |
| Block: 6524 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1362 | RingCT/type: yes/0 |
| Extra: 017f0291f2de20934ec370a5e82bcdc4fbaf28a6dc17e5b1d97520214826e17ae4020900000001e49593ff00 | ||
1 output(s) for total of 34.749332468096 HMNY
| stealth address | amount | amount idx | tag |
| 00: e999eebb6752e6dc80d84f86823253cb798c9d3855d1a3142b002097b478877e | 34.749332468096 | 8026 of 0 | <51> |
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": 6584,
"vin": [ {
"gen": {
"height": 6524
}
}
],
"vout": [ {
"amount": 34749332468096,
"target": {
"tagged_key": {
"key": "e999eebb6752e6dc80d84f86823253cb798c9d3855d1a3142b002097b478877e",
"view_tag": "51"
}
}
}
],
"extra": [ 1, 127, 2, 145, 242, 222, 32, 147, 78, 195, 112, 165, 232, 43, 205, 196, 251, 175, 40, 166, 220, 23, 229, 177, 217, 117, 32, 33, 72, 38, 225, 122, 228, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}