Fix transaction history when using public node clients

[jbrauck-unchained]

What kind of change does this PR introduce?

This applies a fix to transaction history table when using a public node client like mempool.space or blockstream.

Issue Number:

Fixes #410

Snapshots/Videos:

If relevant, did you update the documentation?

Summary

This is a fix to help unblock my PR #394
I purely copied the private client deduplication logic to the public client function.

Does this PR introduce a breaking change?

Checklist

• I have tested my changes thoroughly.
• I have added or updated tests to cover my changes (if applicable).
• I have verified that test coverage meets or exceeds 95% (if applicable).
• I have run the test suite locally, and all tests pass.
• I have written tests for all new changes/features
• I have followed the project's coding style and conventions.
• I have created a changeset to document my changes (npm run changeset)

Other information

Have you read the contributing guide?

For information on creating and using changesets, please refer to our documentation on changesets.

[vercel]

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

Project	Deployment	Review	Updated (UTC)
caravan-coordinator	Ready	Preview, Comment	Dec 24, 2025 6:01pm

[changeset-bot]

⚠️ No Changeset found

Latest commit: f44ea0d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR