Explorer Transaction Fee Mismatch (Wallet vs Explorer)

[cshein45]

✅ Issue Titles (Choose One)

1. Explorer Transaction Fee Mismatch (Wallet vs Explorer)
2. Gas Fee Display Error on Movement Explorer
3. Explorer Shows Lower Fee Than Actual Wallet Deduction
4. Transaction Fee Reporting Incorrect by 0.000001 MOVE
5. Mismatch in FeeStatement vs Wallet-Charged Fee

---

✅ Full Issue Description (Copy & Paste Into GitHub)

## 🐞 Bug Report: Transaction Fee Mismatch on Movement Explorer

### ❗ Issue Summary
The transaction fee shown on the Movement Network Explorer is different from the fee actually deducted by the wallet (MetaMask).  
The difference is consistently **0.000001 MOVE**.

### 🔍 Steps to Reproduce
1. Execute any transaction on Movement Mainnet using a dApp (MovePosition.xyz, Meridian.money, etc.)
2. Copy the transaction hash.
3. Open it in Movement Explorer.
4. Compare:
   - **Explorer → Transaction Fee**
   - **Wallet → Actual fee deducted**

### 🎯 Expected Behavior
The Transaction Fee displayed on the Explorer should match the final fee charged to the user’s wallet.

### ❌ Actual Behavior
The Explorer displays **0.000001 MOVE less** than the amount deducted by the wallet.

### 📌 Example Case
Provide your own tx hash here:

0xfb02380d58a449965c76d8f9361f5d88c8f2fb32659a69f975742551f6cd156b

### 🧪 FeeStatement Breakdown
From Move VM logs:

execution_gas_units: 122
io_gas_units: 126
storage_fee_octas: 98800
storage_fee_refund_octas: 0
total_charge_gas_units: 1235

### 🧩 Suspicion
Explorer may be **rounding down 1 octa (1e-6)** OR missing the **storage_fee_octas calculation**.

Wallet calculates:

gas_price * total_charge_gas_units + storage_fee_octas

Explorer might be using:

gas_price * total_charge_gas_units (missing storage fee)

### 💻 Environment
- Network: Movement Mainnet
- Explorer: https://explorer.movementnetwork.xyz/?network=mainnet
- Browser: Chrome v120.0.6099.200
- Wallet: MetaMask v10.30.0

### 📸 Screenshots
(Insert screenshots or links here)

---

### ✅ Additional Notes
This bug affects:
- Users verifying gas fees
- dApp developers using the explorer for debugging
- Transparency of Movement ecosystem

Fixing it ensures accurate fee reporting across the network.

---

[cshein45]

The explorer is displaying a fee that is 1 octa (0.000001 MOVE) lower than the actual wallet deduction.

From the FeeStatement:

• total_charge_gas_units = 1235
• storage_fee_octas = 98800

It looks like the explorer is calculating:
gas_price * total_charge_gas_units
but is not adding:
+ storage_fee_octas

Wallet includes the storage fee, but the explorer currently displays only the gas component. This is causing the consistent 0.000001 MOVE difference.

Explorer team should verify the final fee calculation formula:
final_fee = (gas_price * total_charge_gas_units) + storage_fee_octas

[cshein45]

Explorer Shows Lower Fee Than Actual Wallet Deduction

The Movement Explorer displays a transaction fee that is slightly lower than the amount actually deducted by the wallet (MetaMask or other wallets).

After reviewing the FeeStatement, it looks like the explorer is only showing the gas-based fee, but not including the storage fee component.

From transaction FeeStatement:

• execution_gas_units = 122
• io_gas_units = 126
• storage_fee_octas = 98800
• total_charge_gas_units = 1235

Wallets calculate the final fee as:

final_fee = (gas_price * total_charge_gas_units) + storage_fee_octas

But the explorer seems to be calculating only:

displayed_fee = gas_price * total_charge_gas_units

This missing storage_fee_octas causes the consistent 0.000001 MOVE difference.

Request:
Please update the explorer fee calculation to include the storage fee so the displayed fee matches the wallet deduction.

[cshein45]

### Transaction Fee Reporting Incorrect by 0.000001 MOVE

The explorer’s displayed transaction fee is consistently lower than the actual fee deducted by the wallet.

Based on the FeeStatement data, the explorer appears to be omitting the `storage_fee_octas` component from the final fee calculation.

**FeeStatement values from the transaction:**
- execution_gas_units: 122  
- io_gas_units: 126  
- total_charge_gas_units: 1235  
- storage_fee_octas: 98800  

Wallets compute the final fee using:

final_fee = (gas_price * total_charge_gas_units) + storage_fee_octas

However, the explorer is currently calculating:

displayed_fee = gas_price * total_charge_gas_units

Since `storage_fee_octas` is not included in the displayed result, the explorer shows a fee that is exactly **0.000001 MOVE** lower than the amount actually charged.

**Request:**  
Please update the explorer to include the storage fee in the final displayed transaction fee so it matches the wallet deduction.

---

[cshein45]

Mismatch in FeeStatement vs Wallet-Charged Fee

There is a consistent mismatch between the fee shown in the Explorer and the amount actually deducted by the wallet.

The Explorer appears to only use total_charge_gas_units for its fee calculation, but does not include storage_fee_octas.

FeeStatement breakdown from the transaction:

• total_charge_gas_units: 1235
• storage_fee_octas: 98800

Wallet fee formula:

wallet_fee = (gas_price * total_charge_gas_units) + storage_fee_octas

Explorer fee formula (current):

explorer_fee = gas_price * total_charge_gas_units

Because storage_fee_octas is missing from the explorer display, the explorer always shows a fee 0.000001 MOVE lower than the actual charged fee.

Expected: Explorer should include the storage fee in the final fee output.