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: f6e4961a713afb5dbcb3c0d0e4f0600e14ce3310d394305fe26086e2481be7e1
Tx prefix hash: e514a2efa5adec044e7dba6b0d008f804dd2145b4da366c99a91dbb42ce09f3a
Tx public key: c7edc595089357958875df05a531526b77b90903af1b122d3a12188c47bfdb31
| Timestamp: 1779718827 | Timestamp [UTC]: 2026-05-25 14:20:27 | Age [y:d:h:m:s]: 00:014:08:58:26 |
| Block: 1711 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6175 | RingCT/type: yes/0 |
| Extra: 01c7edc595089357958875df05a531526b77b90903af1b122d3a12188c47bfdb31020900000001ba6d17be00 | ||
1 output(s) for total of 35.099393561528 HMNY
| stealth address | amount | amount idx | tag |
| 00: 147d674443f09c1caa7a15a8de135268036a219de7ad11839ddffb19fcb5089c | 35.099393561528 | 1882 of 0 | <90> |
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": 1771,
"vin": [ {
"gen": {
"height": 1711
}
}
],
"vout": [ {
"amount": 35099393561528,
"target": {
"tagged_key": {
"key": "147d674443f09c1caa7a15a8de135268036a219de7ad11839ddffb19fcb5089c",
"view_tag": "90"
}
}
}
],
"extra": [ 1, 199, 237, 197, 149, 8, 147, 87, 149, 136, 117, 223, 5, 165, 49, 82, 107, 119, 185, 9, 3, 175, 27, 18, 45, 58, 18, 24, 140, 71, 191, 219, 49, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}