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: bbd42b333d034b4fa907ae8687ffc4fb2919e169f1b4792c9b23856daeee3a57
Tx prefix hash: fb0229139df8ef57db3939ff1d8c2e0b29feea8835e50be8f7cd2b2dc8ee8b7b
Tx public key: 174fbbd0a476b57c94a45fa84fc798029fba7367879724235370b3bb6078188e
| Timestamp: 1779917296 | Timestamp [UTC]: 2026-05-27 21:28:16 | Age [y:d:h:m:s]: 00:012:19:40:47 |
| Block: 3325 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5409 | RingCT/type: yes/0 |
| Extra: 01174fbbd0a476b57c94a45fa84fc798029fba7367879724235370b3bb6078188e02090000000226697be300 | ||
1 output(s) for total of 34.967022456029 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7492e27204631c243d1d6e8e580d198229be8fa8e6640897b1e93a4b6ed1ecdb | 34.967022456029 | 3993 of 0 | <6d> |
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": 3385,
"vin": [ {
"gen": {
"height": 3325
}
}
],
"vout": [ {
"amount": 34967022456029,
"target": {
"tagged_key": {
"key": "7492e27204631c243d1d6e8e580d198229be8fa8e6640897b1e93a4b6ed1ecdb",
"view_tag": "6d"
}
}
}
],
"extra": [ 1, 23, 79, 187, 208, 164, 118, 181, 124, 148, 164, 95, 168, 79, 199, 152, 2, 159, 186, 115, 103, 135, 151, 36, 35, 83, 112, 179, 187, 96, 120, 24, 142, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}