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: 37af166670a8859482f075c08d4216e599476e9b7cc77b44ab0cd5eb6ffc4f27
Tx prefix hash: 93f5e259cee3dcbea2855b6f8e549b776ed825751d8a1752e42c3184a71fc921
Tx public key: a18cefa0928c62238571fb8d648b4cb183e61a5b2121dad62aef1d3820d18429
| Timestamp: 1779932988 | Timestamp [UTC]: 2026-05-28 01:49:48 | Age [y:d:h:m:s]: 00:011:23:46:09 |
| Block: 3416 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4470 | RingCT/type: yes/0 |
| Extra: 01a18cefa0928c62238571fb8d648b4cb183e61a5b2121dad62aef1d3820d1842902090000000326697be300 | ||
1 output(s) for total of 34.955939865734 HMNY
| stealth address | amount | amount idx | tag |
| 00: ce8500816ee7cf144d2c9746c6467a8e61fe9070adff6e697daf44d2196ee5af | 34.955939865734 | 4131 of 0 | <b2> |
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": 3476,
"vin": [ {
"gen": {
"height": 3416
}
}
],
"vout": [ {
"amount": 34955939865734,
"target": {
"tagged_key": {
"key": "ce8500816ee7cf144d2c9746c6467a8e61fe9070adff6e697daf44d2196ee5af",
"view_tag": "b2"
}
}
}
],
"extra": [ 1, 161, 140, 239, 160, 146, 140, 98, 35, 133, 113, 251, 141, 100, 139, 76, 177, 131, 230, 26, 91, 33, 33, 218, 214, 42, 239, 29, 56, 32, 209, 132, 41, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}