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: b5ff28e00605de742928606dd58b870e4e8534d1c6ab14a3d5d04576348aa523
Tx prefix hash: a40ecc449b4e702890f8ef276aaf9a9c9bb033af3a1209b025e689b9bb029fe1
Tx public key: e50c2e545d0e71b2f991eee4572aa1e46814f80fe90c3a4ae0a407c032a05c20
| Timestamp: 1779968815 | Timestamp [UTC]: 2026-05-28 11:46:55 | Age [y:d:h:m:s]: 00:011:13:49:02 |
| Block: 3830 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4056 | RingCT/type: yes/0 |
| Extra: 01e50c2e545d0e71b2f991eee4572aa1e46814f80fe90c3a4ae0a407c032a05c2002090000000726697be300 | ||
1 output(s) for total of 34.928348044747 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4a25f346ece9143254dbd37ef9b9c83bc9229888255381614dadb215de0d6b5d | 34.928348044747 | 4667 of 0 | <33> |
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": 3890,
"vin": [ {
"gen": {
"height": 3830
}
}
],
"vout": [ {
"amount": 34928348044747,
"target": {
"tagged_key": {
"key": "4a25f346ece9143254dbd37ef9b9c83bc9229888255381614dadb215de0d6b5d",
"view_tag": "33"
}
}
}
],
"extra": [ 1, 229, 12, 46, 84, 93, 14, 113, 178, 249, 145, 238, 228, 87, 42, 161, 228, 104, 20, 248, 15, 233, 12, 58, 74, 224, 164, 7, 192, 50, 160, 92, 32, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}