audit

The other pages interpret. This one does not. It lists signatures and lets you open each one to see the raw instruction data, accounts, balances, and log. If you suspect that an interpreted page is wrong, this is where you check. If you find that it is, that is a serious incident and I would like to know, by helpdesk memo.

The cluster returns signatures in pages, newest first, and the RPC provider may not hold the full history of the program. The listing goes back as far as the provider does. A complete history would require an archive node, and this site does not assume one. Where the listing ends, it says so.

Each instruction's data begins with an eight-byte discriminator that identifies the instrument, followed by its arguments in the order the interface lists them, each as a fixed-width little-endian integer except name, which is a length-prefixed string. The detail page decodes these using the published interface. If the interface cannot be fetched, the detail page shows the bytes in hexadecimal and nothing else.