Add transaction history pagination

[Miracle656]

Summary

The dashboard currently shows the most recent transactions but has no pagination. Add a 'Load more' button or infinite scroll.

Files

• frontend/wallet/app/dashboard/page.tsx

Acceptance criteria

• Track current page / cursor in state
• Horizon supports cursor pagination — pass through
• Wraith supports limit/offset — pass through
• 'Load more' merges new entries into existing list
• No duplicates when both sources return same tx

[arya23923]

May I be assigned this issue?

[Miracle656]

Thanks for the interest! Before I assign, could you share a brief plan — which files you'd touch, how you'd thread the cursor through the Horizon + Wraith merge, and how you'll avoid duplicates? Doesn't need to be long, just enough to confirm you've looked at dashboard/page.tsx.

[arya23923]

Hey so I've gone through dashboard/page.tsx and from my understanding the current implementation has a hardcoded limit(20) from Horizon and limit=20 form Wraith which is then merged, deduplicated by hash and then sliced to 30. So there doesn't seem to be any need for touching other files except the above and avoiding duplicate values has also been implemented.

So the further work that needs to be done is adding new state variables to store pagination_token from Horizon or the last transaction fetched, one to store how many variables have been loaded from Wraith, a load more variable and a variable preventing users from clicking on the load button when details are being fetched.

I also plan on splitting the fetchData into two functions - one being the initial load and the other being the load more functionality.

This is the skeleton of the plan as of now. Thank you for the consideration!!

[Miracle656]

Good plan — you clearly read the code. Go ahead, you're assigned. A couple notes:

• Horizon cursor-based pagination uses cursor param (the paging_token from the last record). Wraith uses offset + limit.
• Make sure the 'Load more' button is disabled while fetching (you mentioned this — good).
• Keep the dedup-by-hash logic working across pages.

Open a draft PR early so we can review as you go.