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: fc276e023c6363347dfa8909c1f1a97af6a6c3026905cb565bd6075e8a3f5e72
Tx prefix hash: ab4181946f8c319dd57c964fe512a81997a10d5f843223d2c08cd81eb88c3904
Tx public key: de3857c9aa070fe7150c6b67ba1c180ee39509af28e5a5cf1b1353dcf8f6f9c5
| Timestamp: 1779797860 | Timestamp [UTC]: 2026-05-26 12:17:40 | Age [y:d:h:m:s]: 00:013:13:18:17 |
| Block: 2280 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5606 | RingCT/type: yes/0 |
| Extra: 01de3857c9aa070fe7150c6b67ba1c180ee39509af28e5a5cf1b1353dcf8f6f9c502090000000126697be300 | ||
1 output(s) for total of 35.031762767373 HMNY
| stealth address | amount | amount idx | tag |
| 00: 55f80c45310dfff2b82e9931d7e0a3ff3d1e94025fae3a214d3497ec8721f3ad | 35.031762767373 | 2654 of 0 | <59> |
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": 2340,
"vin": [ {
"gen": {
"height": 2280
}
}
],
"vout": [ {
"amount": 35031762767373,
"target": {
"tagged_key": {
"key": "55f80c45310dfff2b82e9931d7e0a3ff3d1e94025fae3a214d3497ec8721f3ad",
"view_tag": "59"
}
}
}
],
"extra": [ 1, 222, 56, 87, 201, 170, 7, 15, 231, 21, 12, 107, 103, 186, 28, 24, 14, 227, 149, 9, 175, 40, 229, 165, 207, 27, 19, 83, 220, 248, 246, 249, 197, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}