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: 78e78bb196c9320a684691492b4134849cdff2cd72e24e2c1fbab8c9cef48b9f
Tx prefix hash: 7c90a5de7cc66bef82209e4407d61853a5c5f979d7fcf01a7b3d6261869d7faf
Tx public key: 8861b047e65475f48eef06e2ac3e268b9e7435643ba8db9deb02bc9b80261979
| Timestamp: 1780055498 | Timestamp [UTC]: 2026-05-29 11:51:38 | Age [y:d:h:m:s]: 00:010:14:48:58 |
| Block: 4449 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3447 | RingCT/type: yes/0 |
| Extra: 018861b047e65475f48eef06e2ac3e268b9e7435643ba8db9deb02bc9b8026197902090000000626697be300 | ||
1 output(s) for total of 34.887134227417 HMNY
| stealth address | amount | amount idx | tag |
| 00: 95ef777bea6c1c43945931fd8122456dd16b8af87d3dd3c580f391b36e3feaf2 | 34.887134227417 | 5569 of 0 | <72> |
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": 4509,
"vin": [ {
"gen": {
"height": 4449
}
}
],
"vout": [ {
"amount": 34887134227417,
"target": {
"tagged_key": {
"key": "95ef777bea6c1c43945931fd8122456dd16b8af87d3dd3c580f391b36e3feaf2",
"view_tag": "72"
}
}
}
],
"extra": [ 1, 136, 97, 176, 71, 230, 84, 117, 244, 142, 239, 6, 226, 172, 62, 38, 139, 158, 116, 53, 100, 59, 168, 219, 157, 235, 2, 188, 155, 128, 38, 25, 121, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}