Routebook

Inspect Transactions

Routebook turns a raw transaction into something you can read: a tree of the calls it made, with decoded arguments, token movements, events and the reason it failed if it did.

Decode a transaction

1
Select the network
Routebook reads the network selected in the sidebar.
2
Paste the hash
Open Inspect Tx and paste a transaction hash: 66 characters starting with 0x. The overview has a decode box too.
3
Read the result
The call tree, decoded parameters, transfers and events appear. Addresses with a label are shown by name.

What you see

The top-level call and every internal call it made, nested in order.
Function names and arguments decoded, instead of raw calldata.
Native and token transfers: who sent what to whom.
Emitted events, with their parameters.
The revert reason, when a transaction failed.
Names from the Label Registry in place of addresses.

Every deploy success screen links straight to Routebook. To name a contract you see here, add it to the Label Registry.