[Bug]: Receive confetti displays for old transaction when Electrum reconnects

[catch-21]

Describe the bug

When the connection to Electrum drops and reconnects, I quite often see the confetti screen for a transaction that I received a while ago, possibly even days ago. This issue is fully reproducible. It will celebrate for a transaction I've already seen the confetti for, although, I cannot find the pattern for what transaction is decides to celebrate for.

Reproduce

This has occurred quite a few times for me recently under normal usage so I am confident it would occur in the wild, which could be confusing for users. These steps recreate it for me reliably (same as attached screengrab vid):

1. Open Bitkit with a wallet that has some received on-chain transactions
2. Go to Electrum Server settings
3. Cease all internet connection (airplane mode)
4. Wait for "Electrum Connection Failed" message
5. Allow internet connection again
6. Wait for "Internet Connection Restored"
7. Tap "Connect To Host" button (may need to leave Electrum Server settings screen and come back for it to be enabled)
8. Observe "Received Bitcoin" confetti screen for a transaction that happened some time ago and you have probably already celebrated.

Screenshots / Recording

confetti_again.mp4

Operating system

Android 13 TKQ1.220829.002

Bitkit version

c55c045

Log output

No response

[catch-21]

This happens often to me on wallet restore, so not just in normal use and electrum server reconnects.

[catch-21]

This appears to be fixed now, possibly by https://github.com/synonymdev/bitkit/pull/2210

[catch-21]

I have recently seen this again when using v1.0.5 (136), but not on wallet restore. It was after initiating a manual transfer, possibly electrum disconnected and reconnected. The UTxO (75201f594cf6fdd1799fa1d5b5741a7ef81347420ff3f861217be97ead88aceb:0 value of 377) it displayed the value for from back in 29th May:

My hunch is that there are multiple refreshes coinciding when Electrum reconnects, which is similar to what was reliably happening on wallet restore before the recent fix.