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: 6494569396a7dacb3c45e461f4791e01570ccf0ed4591605998f66a836997ba4
Tx prefix hash: 42472e4b9f4f3509698e74c8a617a5fc4a9c14bcdd3219978c4d5e4895504ab8
Tx public key: bc6c740b74ffc78b34cabb38ae24418d7603536c78b799d9dff875e87e000ea8
| Timestamp: 1780059818 | Timestamp [UTC]: 2026-05-29 13:03:38 | Age [y:d:h:m:s]: 00:010:13:36:58 |
| Block: 4503 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3394 | RingCT/type: yes/0 |
| Extra: 01bc6c740b74ffc78b34cabb38ae24418d7603536c78b799d9dff875e87e000ea802090000000326697be300 | ||
1 output(s) for total of 34.883541144932 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2dae4271905026e1ac1b800da072ea51120c792dced04156a1dd144cac6cc65a | 34.883541144932 | 5645 of 0 | <1a> |
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": 4563,
"vin": [ {
"gen": {
"height": 4503
}
}
],
"vout": [ {
"amount": 34883541144932,
"target": {
"tagged_key": {
"key": "2dae4271905026e1ac1b800da072ea51120c792dced04156a1dd144cac6cc65a",
"view_tag": "1a"
}
}
}
],
"extra": [ 1, 188, 108, 116, 11, 116, 255, 199, 139, 52, 202, 187, 56, 174, 36, 65, 141, 118, 3, 83, 108, 120, 183, 153, 217, 223, 248, 117, 232, 126, 0, 14, 168, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}