Quote from: NotATether on Today at 10:58:54 AM

Your app appears to be broken for your example address but from looking at the sample picture, it's a good concept.

What happens exactly ? Does it freeze or does the API reject your call ?
The exemple address has another transaction with a lot of inputs, since I render a node for every input address, that might cause your the app to freeze (I should at least put a warning). It works for me tho, here's what I get :
https://ibb.co/PmGrhMT

Did you try with any other address ?

Quote from: NotATether on Today at 10:58:54 AM

If you hosted this thing server-side, which would require you to move this from Github Pages to an actual server, then you could be able to make a graph data structure of addresses as they are passed to you, and you wouldn't need to perform rate-limiting API calls each time someone makes a request to your app.

I considered the question. I just wanted to make a PoC here, using an external API.
I have different ideas for the backend and but I want something easy to deploy for anyone on their own node (so they could read their own chain) if they want (and a demo saas version).
I'll post updates here

Quote from: NotATether on Today at 10:58:54 AM

Or, you could preload the last N transactions, and create some sort of back button that will load the previous N transactions for a particular transaction output and so on.

It's actually implemented. The '+' button in an addres loads all of it's transactions and the target addresses. You can dig in the direction you want (until you have a big transaction that crashes the app lol)