We should have a page for every taddr address, where people can look up it's tx history. This is mostly useful for miners or people with very old addresses from before z2z.
We can have a search input box which simply does a GET for a URL like /address/Rsomeaddress and let nginx return a 404 if it does not exist.
This will increase the HD disk usage of the explorer by a good amount.
We should have a page for every taddr address, where people can look up it's tx history. This is mostly useful for miners or people with very old addresses from before z2z.
We can have a search input box which simply does a GET for a URL like /address/Rsomeaddress and let nginx return a 404 if it does not exist.
This will increase the HD disk usage of the explorer by a good amount.
Some addresses have a huge number of tx's and so we likely should create pages, such as 500 tx's per page for each address. In particular, the devtax address has 1 tx per block, so it's go close to 1 million tx's. We cannot render all tx's on a single page for the devtax address.
Some addresses have a huge number of tx's and so we likely should create pages, such as 500 tx's per page for each address. In particular, the devtax address has 1 tx per block, so it's go close to 1 million tx's. We cannot render all tx's on a single page for the devtax address.
We should have a page for every taddr address, where people can look up it's tx history. This is mostly useful for miners or people with very old addresses from before z2z.
We can have a search input box which simply does a GET for a URL like /address/Rsomeaddress and let nginx return a 404 if it does not exist.
This will increase the HD disk usage of the explorer by a good amount.
Some addresses have a huge number of tx's and so we likely should create pages, such as 500 tx's per page for each address. In particular, the devtax address has 1 tx per block, so it's go close to 1 million tx's. We cannot render all tx's on a single page for the devtax address.