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: e1b4698a2744ab03ab792889e650367f5af0f26ddcb6a1524965f0fb83352eed
Tx prefix hash: 9290ed3e4b120b1d220058e4fd9459e98d5aa65f99c3fb6089a2a1ccbdc8b7c8
Tx public key: c4e679e2218705dba5f8b6a64e4335b22ec9c529d4eca80714c4d851a57e8645
| Timestamp: 1779920450 | Timestamp [UTC]: 2026-05-27 22:20:50 | Age [y:d:h:m:s]: 00:012:04:28:58 |
| Block: 3351 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4569 | RingCT/type: yes/0 |
| Extra: 01c4e679e2218705dba5f8b6a64e4335b22ec9c529d4eca80714c4d851a57e864502090000000526697be300 | ||
1 output(s) for total of 34.960273894191 HMNY
| stealth address | amount | amount idx | tag |
| 00: c95ae79c606665b1871e6fd9d874b6ba3a0c1654229f7ff8fba0962050fa9003 | 34.960273894191 | 4032 of 0 | <34> |
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": 3411,
"vin": [ {
"gen": {
"height": 3351
}
}
],
"vout": [ {
"amount": 34960273894191,
"target": {
"tagged_key": {
"key": "c95ae79c606665b1871e6fd9d874b6ba3a0c1654229f7ff8fba0962050fa9003",
"view_tag": "34"
}
}
}
],
"extra": [ 1, 196, 230, 121, 226, 33, 135, 5, 219, 165, 248, 182, 166, 78, 67, 53, 178, 46, 201, 197, 41, 212, 236, 168, 7, 20, 196, 216, 81, 165, 126, 134, 69, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}