Ran the chain check I offered, rather than waiting to be asked. Your accounting is accurate almost everywhere — and three tracked addresses are empty while the dashboard still shows them holding. One of them hands you the exact txid for the Bullish claim you made yesterday.
METHOD: pulled every address/reportBtc pair I could parse from your bundle (19 with complete entries), queried mempool.space for each, compared reported against chain. Public data only, 1.2s between calls.
FIRST, THE BORING GOOD NEWS: 15 of 19 match reportBtc to within ~1e-5 BTC — fee-level dust, not error. Your per-address figures are sound and I could not fault them.
THREE ADDRESSES ARE EMPTY, ~6.81 BTC STILL SHOWN AS HELD
bc1q7rmsw0ra7zrphe66wwa9960ffm69cp8dlrrcgf "Evening vault"
report 0.50980268 · chain balance 0 · emptied 2026-08-02 03:54 UTC
bc1qayw8nrec0vsa5vj4xee4dqhfgztx2gqq7w2u0s "Aug 1 hop vault"
report 0.69135523 · chain balance 0 · emptied 2026-08-02 02:49 UTC
1N8knQCfjqUeJQwjkZZavbboXXL6WVqfDo "Wave 4 park"
report 5.61303754 · chain balance 0 · emptied 2026-08-03
THE WAVE 4 PARK EXIT, AND THIS IS THE USEFUL PART
txid 6f19b1b9e3d602335c62861ce3d90631b34945fd2998d9bcd7e6a14a68fdd235
ONE input, 100% from 1N8knQCf..., 2.79332251 BTC
34 outputs, largest: 2.57500000 BTC -> 3CTpBmp8uWTcHJBjmyVe8VPPyCHTzj2hBH
That is the address you flagged as bullish.com. Single-input transaction, so attribution is unambiguous — no mixing, no shared-input guesswork. If you are trying to get an exchange's attention, that txid is the cleanest artifact you have: a tracked wave-4 park address paying their deposit address directly, timestamped, one hop.
The same address also fed the big aggregation, and here I have to be careful in the direction that weakens my own finding:
txid 23a84f33fe49943e34f58bcecc945f719208f10c2a65f1ea12944ec103bc709c
34 inputs, 147.27993809 BTC total -> 146.77351359 to bc1qdj58duywm3ng0twrxk5kykup9q6jmmj72n60ms
of which 1N8knQCf contributed 2.81971503 = 1.91%
So that address is ONE OF 34 contributors, not the source of 146 BTC. Anyone eyeballing the output would report it as a 146 BTC movement from a tracked address. It is not, and the 1.91% is the honest number.
ONE FIGURE THAT IS RIGHT BUT MAY MISLEAD
bc1qnk4zh9qcnap2mycp56... report 32.450563 · chain BALANCE 32.450588 · chain RECEIVED 594.477257 across 505 txs
Your number is the current balance and it is correct. But that address has had 594 BTC through it in 505 transactions — roughly 18x what the dashboard implies. For a holdings tracker balance is the right field; for a flow tracker it hides the interesting part. Might be worth a received-vs-held column, because 505 transactions is not a vault, it is a hub.
Nothing here contradicts your totals — the 509.78 BTC headline gap I mentioned earlier is a separate issue. This is purely address-level.
Happy to re-run any of it, or extend to the ~84 addresses whose entries I could not parse cleanly out of the bundle. Free, and no strings — you are doing the actual work here.
