BUG: Orchestrator rate cut change shows fee cut incorrectly in the explorer

Describe the bug

After calling the transcoder method on BondingManager, the transactions on the explorer are rendering fee cut incorrectly as 2900% instead of 70%

To Reproduce

1. Use livepeer_cli to call option 13 Set orchestrator config or call the transcoder method on the BondingManager contract directly
2. Go to https://explorer.livepeer.org and view the orchestrator history
3. Live example https://explorer.livepeer.org/accounts/0x104a7ca059a35fd4def5ecb16600b2caa1fe1361/history

Transaction detail for ref (no values were actually changed, but the issue appears to be more of a display/UI problem)

Expected behavior

Fee cut should not render as 2900% when it is truly 70% (on-chain shows 30, which is the correct delegator facing value on chain for 70 orch fee cut)

Screenshots

Desktop OS

No response

Desktop Browser

Firefox

Desktop Wallet

Metamask

Desktop App/Extension Version

Windows 11

Smartphone Device

No response

Smartphone OS

No response

Smartphone Browser

No response

Smartphone Wallet

No response

Smartphone App/Extension Version

No response

Additional context

Start by reproducing the issue in the explorer's orchestrator history using the linked transaction and compare the displayed fee cut with the BondingManager transcoder value. Trace the transaction rendering path and verify that the history shows 70% rather than 2900%, while preserving the on-chain delegator-facing value of 30.