I found this as an external option https://graphql-api.mainnet.dandelion.link/. But is there anything that can be done locally? I have a relay node running. I can build and send transactions. Basically I want the data that’s in every explorer such as https://cardanoscan.io/.
Or is there a simpler way since it’s the infrastructure is fairly complex. I’m not quite sure what you mean by via cardano-db-sync? Do you have any docs or more concrete steps?
It is simply a postgres DB with a node and a daemon, I’d say it’s pretty basic for blockchain architecture. You can find doco for each component at https://docs.cardano.org.
But if you’re simply looking to leverage off someone else’s node, then you can checkout https://blockfrost.io or https://dandelion.link
Newbie here – I have a node and wallet running and have also set up cardano-dy-sync-exented on my machine, and am curious on how exactly to query the transaction details of my wallet? I can locally query my wallet’s UTxOs and find respective txHash, but am stumped on how to find the sender’s address associated to the various txHashes. I have tried various queries such as
select tx_out.* from tx_out inner join tx on tx_out.tx_id = tx.id where tx.hash = '<my transaction hash>' ;
and
select tx_out.* from tx_out inner join tx_in on tx_out.tx_id = tx_in.tx_out_id inner join tx on tx.id = tx_in.tx_in_id and tx_in.tx_out_index = tx_out.index where tx.hash = '<my transaction hash>' ;
but always end up with an empty output.
Any insight would be appreciated
I guess you took that SQL from the reference given in the official doc. I tried the same query but could not determine which one is the sender and which ones are the receivers.
Easiest way to consume that information would be to use our new and free public API.
We first brought it online today, and the node still has to synchronize a bit more - but it’s still usable to some extend and will be fully available in the next days (including live data).
We will improve that documentation over the next days.
Bear in mind that the API still needs to synchronize and is some days behind.
We started testing our API today, if you find some issues - feel free to report via github.