Mintscan

Mintscan’s historical API is useful when the question concerns a period rather than a current balance. Its account-balance-history request takes a network and address, plus optional start and end times. The default window is the last thirty days. Use the returned searchAfter value to continue through older result pages, and adjust take to control page size. Authentication uses an access token.

The API catalogue distinguishes historical data from statistics, search and transaction-building operations. It also assigns different credit costs to queries. Confirm the supported network and your access allowance before treating a balance-history request as interchangeable with a lightweight lookup. Current onboarding directs new users to register and seek email approval.

Publishing inspectable contract code

For a CosmWasm contract, the verification form asks for an optimizer type and version, repository URL and branch. After Verify, copy the returned queue identifier into Result ID under Check Verification to retrieve the outcome. The process compares the built code checksum with the deployed code. Projects using an unsupported compiler or missing the expected schema command cannot use this verification route.

Ethereum-compatible verification follows a different path. The guide uses the contract’s code page on Kavascan or a Hardhat configuration for Kava. Select the contract environment before following either procedure. A successful code match makes the implementation inspectable; it does not establish that the contract is free of defects or economically safe.