fix(tx): proper calculation of loaded account sizes for transaction v1

[tiago18c]

Description

Total Account Size has incorrect values as it related to transaction v1 header (missing program data size and 64 byte overhead). This PR correctly calculates the Loaded Account Data Size according to SIMD-0186 and displays it next to the v1 size request. On LEGACY and V0 the value is left on the Accounts Card.

Preview:

A V1 transaction:

A LEGACY transaction

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge; the updated test waits match how account rows are fetched.

Summary

The PR counts program data and adds the 64-byte account charge when showing v1 loaded data beside its limit. Earlier transaction versions keep their total on the Accounts card.

• Loaded-account totals include program data and 64-byte charges.
• V1 summaries compare loaded data with the declared limit.
• Inspector account totals use the loaded-account sizes.

_{Reviews (2) · Last reviewed commit: "fix(tx): fixed the flaky test" · Reviewed by Greptile}

[vercel]

@tiago18c is attempting to deploy a commit to the Solana Foundation Team on Vercel.

A member of the Team first needs to authorize it.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
explorer	Ready	Preview	Oct 12, 2026 5:07pm UTC