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: 7b94584cb2a9361658ec9a90a8dfc362167514285218410c018f9c0e5bd91207
Tx prefix hash: 0d40ebf0f5b95031ddfb77cfca7469fde1819a4385e71e96581dd5e695362eca
Tx public key: 13e995f41cb859caefb1c395dd99fa1a5c855f47ba7f1b8241d01ac119afb747
| Timestamp: 1779735476 | Timestamp [UTC]: 2026-05-25 18:57:56 | Age [y:d:h:m:s]: 00:014:05:48:51 |
| Block: 1914 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5972 | RingCT/type: yes/0 |
| Extra: 0113e995f41cb859caefb1c395dd99fa1a5c855f47ba7f1b8241d01ac119afb74702090000000326697be300 | ||
1 output(s) for total of 35.056226637941 HMNY
| stealth address | amount | amount idx | tag |
| 00: de294954a3abec51fbbe4d20dbc8a038dc4aa9dca57c1f319c7ecbd30f3707ed | 35.056226637941 | 2146 of 0 | <a1> |
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": 1974,
"vin": [ {
"gen": {
"height": 1914
}
}
],
"vout": [ {
"amount": 35056226637941,
"target": {
"tagged_key": {
"key": "de294954a3abec51fbbe4d20dbc8a038dc4aa9dca57c1f319c7ecbd30f3707ed",
"view_tag": "a1"
}
}
}
],
"extra": [ 1, 19, 233, 149, 244, 28, 184, 89, 202, 239, 177, 195, 149, 221, 153, 250, 26, 92, 133, 95, 71, 186, 127, 27, 130, 65, 208, 26, 193, 25, 175, 183, 71, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}