[Bug]: stardust tx page not loading

[Thoralf-M]

Issue description

https://explorer.iota.org/shimmer-testnet/transaction/0x5455c5f846b90f35d2f49bf2902b2900cbd35b49e3c3166a00b7024152769580 just shows a white page and errors in the browser console

index-3542c4e1.js:11 Uncaught TypeError: Cannot read properties of undefined (reading 'type')
    at Ss.buildAddressFromTypes (App-fbf9cba0.js:69:9081)
    at Ss.buildAddress (App-fbf9cba0.js:69:8720)
    at MT (App-fbf9cba0.js:85:90300)
    at App-fbf9cba0.js:85:89635
    at Array.map (<anonymous>)
    at IT (App-fbf9cba0.js:85:89335)
    at App-fbf9cba0.js:85:105615
    at Bh (index-3542c4e1.js:13:24283)
    at G0 (index-3542c4e1.js:13:42406)
    at e6 (index-3542c4e1.js:13:36624)
    at vs (index-3542c4e1.js:11:3279)
    at Tx (index-3542c4e1.js:13:41283)
    at Ms (index-3542c4e1.js:13:40275)
    at d9 (index-3542c4e1.js:13:35732)
    at V (index-3542c4e1.js:6:39854)
    at MessagePort.o (index-3542c4e1.js:6:40218)

Expected behaviour

Should show the tx page

Actual behaviour

White page + error

Can the issue reliably be reproduced?

Yes

Steps to reproduce the issue

Open https://explorer.iota.org/shimmer-testnet/transaction/0x5455c5f846b90f35d2f49bf2902b2900cbd35b49e3c3166a00b7024152769580

Errors

index-3542c4e1.js:13 TypeError: Cannot read properties of undefined (reading 'type')
    at Ss.buildAddressFromTypes (App-fbf9cba0.js:69:9081)
    at Ss.buildAddress (App-fbf9cba0.js:69:8720)
    at MT (App-fbf9cba0.js:85:90300)
    at App-fbf9cba0.js:85:89635
    at Array.map (<anonymous>)
    at IT (App-fbf9cba0.js:85:89335)
    at App-fbf9cba0.js:85:105615
    at Bh (index-3542c4e1.js:13:24283)
    at G0 (index-3542c4e1.js:13:42406)
    at e6 (index-3542c4e1.js:13:36624)
    at vs (index-3542c4e1.js:11:3279)
    at Tx (index-3542c4e1.js:13:41283)
    at Ms (index-3542c4e1.js:13:40275)
    at d9 (index-3542c4e1.js:13:35732)
    at V (index-3542c4e1.js:6:39854)
    at MessagePort.o (index-3542c4e1.js:6:40218)

Duplicate declaration

• [X] I have searched the issues tracker for this issue and there is none

Code of Conduct

• [X] I agree to follow this project's Code of Conduct