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: 51f499919562fb385d802c419f1f4a6e2a5985890a1a87dae594255475847a3d
Tx prefix hash: fa17d3a8c7075b68a0639e67982a97c38deea9cbe63343a45757a4510df3d59a
Tx public key: ceef95d93a9ec62ef9a14dc5b68e85d45b5e5067965f0196be85dcfc33514776
| Timestamp: 1779858414 | Timestamp [UTC]: 2026-05-27 05:06:54 | Age [y:d:h:m:s]: 00:012:18:11:59 |
| Block: 2645 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5241 | RingCT/type: yes/0 |
| Extra: 01ceef95d93a9ec62ef9a14dc5b68e85d45b5e5067965f0196be85dcfc3351477602090000000126697be300 | ||
1 output(s) for total of 35.007382740119 HMNY
| stealth address | amount | amount idx | tag |
| 00: b0d622d041489d1d98dec6f99a010c329e343da98f12ccb58104121f15768c36 | 35.007382740119 | 3117 of 0 | <41> |
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": 2705,
"vin": [ {
"gen": {
"height": 2645
}
}
],
"vout": [ {
"amount": 35007382740119,
"target": {
"tagged_key": {
"key": "b0d622d041489d1d98dec6f99a010c329e343da98f12ccb58104121f15768c36",
"view_tag": "41"
}
}
}
],
"extra": [ 1, 206, 239, 149, 217, 58, 158, 198, 46, 249, 161, 77, 197, 182, 142, 133, 212, 91, 94, 80, 103, 150, 95, 1, 150, 190, 133, 220, 252, 51, 81, 71, 118, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}