#Current transaction explorer for futurenet

1 messages · Page 1 of 1 (latest)

rotund peak
#

Is there currently any way to see a list of transactions for an account?

blissful hearth
#

If you filter the txs for type_i = 24 you'll get all the hostInvoke operations

rotund peak
blissful hearth
#

You'll see a lot of type = "invoke_host_function" operations. These are calls/invocations of Soroban Smart Contracts. If you decode the parameters, you can find out which contract Id it was, the function called and its parameters.

forest patrol
#

someone made that site, forget what it was called, soroban fiddle

blissful hearth
forest patrol
#

yeah

hearty sentinel
#

Unfortunately the env got a major refactor just after I built fiddle, and I haven't had any spare time to rework it to get it to work with the new design.

forest patrol
#

ah well no worries.

hearty sentinel
#

@forest patrol Want to take it from me?

forest patrol
#

I'll take a look at it, shouldn't be tooo hard to update

#

it's public right?

#

gimme a link

hearty sentinel
#

⚠️ Warning: Lotsa hacks. So many hacks. 😄

forest patrol
#

Can i run it on cf workers?

#

hacks are usually the best way to make it work when you need to make it work 😆

hearty sentinel
#

It's a static website and so it'll run anywhere I guess. I currently host it on GitHub Pages.

#

It's Rust, but it builds to .html and .wasm files, and then it is static. There's no backend.

forest patrol
#

yeah i saw that after i looked 😄 I'll play with it at some point here

#

what broke did the scvals change

#

interesting how it works, I was just glancing through the code. have you seen tauri

hearty sentinel
#

What's tauri?

forest patrol
#

it's like a rust library for making ui's https://tauri.app/ i havn't really used it but it looks kinda interesting

#

what was the last version of soroban the fiddle was compatible with

#

also am i correct in assuming it opens a stream to horizon to scan transactions, for deploy/invoke? I am thinking there was a change in how contracts are deployed actually since you install an instance of it now but knowing when it was last compatible would help to find whatever is not working properly. At some point i'll build it locally and see what it does now

hearty sentinel
#

Ah right. I used yew which is another lib that does similar.

hearty sentinel
#

It keeps track of what contracts are deployed, as well as their invocations.

#

That way it works is that when you invoke a contract it invokes it's past invocations first to arrive at the same or similar state. All that is flawed and only works for simple contracts really.

forest patrol
#

right. Ideally in my mind it would download the wasm, then parse the interface, but that would require linking a wallet to do live invokes that is. Similar to how etherscan has the write contract page

#

Do you mean streaming the tx from horizon is inefficient or the method by which it's done? I like the fiddle alot, it'd be really nice if it could act like an explorer and keep a database, obviously that would require a bit more than a static site. however if there's a way to just update the parsing it seems like we should be able to get it working on the current version fairly easily. I dunno when i'll get time to mess with it but perhaps can be a diversion from other stuff 😆

hearty sentinel
#

I was trying to have as much fun as possible without having any dependence on a backend or a wallet. 😄

#

Feel free to change anything though.

forest patrol
#

Yeah makes sense just ideas i'm sprouting 😄 at first if i changed anything it'd be just get it working again