> ## Documentation Index > Fetch the complete documentation index at: https://docs.cosmos.network/llms.txt > Use this file to discover all available pages before exploring further. # GetLatestBlockResults > gRPC: `cosmos.base.tendermint.v1beta1.Service/GetLatestBlockResults` ([reference](/sdk/next/api-reference/grpc/base#getlatestblockresults)) GetLatestBlockResults returns the block results for the latest block. Block results contain finalize_block_events which include consensus-level events like slashing, jailing, and validator set updates. ## OpenAPI ````yaml /sdk/next/api-reference/rest/openapi.yaml get /cosmos/base/tendermint/v1beta1/block_results/latest openapi: 3.0.0 info: title: Cosmos SDK REST API description: >- HTTP bindings for the gRPC query services of the standard Cosmos SDK modules, documenting Cosmos SDK v0.55 (unreleased). Generated from cosmos/cosmos-sdk at commit c1126e4e5460571378bf9bd9c49cce476b0791e2 on ref `main`. A chain exposes only the modules its application registers, so it may serve a subset of these routes alongside routes of its own. version: v0.55 (unreleased) servers: - url: https://cosmos-rest.publicnode.com description: >- Community-run public endpoint serving Cosmos Hub. Not operated by the Cosmos SDK team, and running a different SDK version than these pages document. Endpoints for modules the chain does not include return 501. - url: http://localhost:1317 description: Your own node. Requires api.enable in app.toml. security: [] tags: - name: auth - name: authz - name: bank - name: base - name: consensus - name: distribution - name: epochs - name: evidence - name: feegrant - name: gov - name: mint - name: slashing - name: staking - name: tx - name: upgrade paths: /cosmos/base/tendermint/v1beta1/block_results/latest: get: tags: - base summary: GetLatestBlockResults description: >- gRPC: `cosmos.base.tendermint.v1beta1.Service/GetLatestBlockResults` ([reference](/sdk/next/api-reference/grpc/base#getlatestblockresults)) GetLatestBlockResults returns the block results for the latest block. Block results contain finalize_block_events which include consensus-level events like slashing, jailing, and validator set updates. operationId: base_v1beta1_GetLatestBlockResults responses: '200': description: A successful response. content: '*/*': schema: type: object properties: height: type: string format: int64 description: height is the block height. txs_results: type: array items: type: object properties: code: type: integer format: int64 data: type: string format: byte nullable: true log: type: string title: nondeterministic info: type: string title: nondeterministic gas_wanted: type: string format: int64 gas_used: type: string format: int64 events: type: array items: type: object properties: type: type: string attributes: type: array items: type: object properties: key: type: string value: type: string index: type: boolean title: nondeterministic description: >- EventAttribute is a single key-value pair, associated with an event. additionalProperties: false nullable: true description: >- Event allows application developers to attach additional information to ResponseFinalizeBlock and ResponseCheckTx. Later, transactions may be queried using these events. additionalProperties: false title: nondeterministic nullable: true codespace: type: string description: >- ExecTxResult contains results of executing one individual transaction. * Its structure is equivalent to #ResponseDeliverTx which will be deprecated/deleted additionalProperties: false description: >- txs_results contains the results of each transaction execution. nullable: true finalize_block_events: type: array items: type: object properties: type: type: string attributes: type: array items: type: object properties: key: type: string value: type: string index: type: boolean title: nondeterministic description: >- EventAttribute is a single key-value pair, associated with an event. additionalProperties: false nullable: true description: >- Event allows application developers to attach additional information to ResponseFinalizeBlock and ResponseCheckTx. Later, transactions may be queried using these events. additionalProperties: false description: >- finalize_block_events contains consensus-level events emitted during block finalization, including slashing, jailing, and validator set updates. nullable: true validator_updates: type: array items: type: object properties: pub_key: type: object properties: ed25519: type: string format: byte nullable: true secp256k1: type: string format: byte nullable: true title: >- PublicKey defines the keys available for use with Validators nullable: true additionalProperties: false power: type: string format: int64 additionalProperties: false description: >- validator_updates contains the validator updates for this block. nullable: true consensus_param_updates: description: >- consensus_param_updates contains any consensus parameter updates for this block. type: object properties: block: type: object properties: max_bytes: type: string format: int64 title: |- Max block size, in bytes. Note: must be greater than 0 max_gas: type: string format: int64 title: |- Max gas per block. Note: must be greater or equal to -1 description: BlockParams contains limits on the block size. nullable: true additionalProperties: false evidence: type: object properties: max_age_num_blocks: type: string format: int64 description: >- Max age of evidence, in blocks. The basic formula for calculating this is: MaxAgeDuration / {average block time}. max_age_duration: type: string description: >- Max age of evidence, in time. It should correspond with an app's "unbonding period" or other similar mechanism for handling [Nothing-At-Stake attacks](https://github.com/ethereum/wiki/wiki/Proof-of-Stake-FAQ#what-is-the-nothing-at-stake-problem-and-how-can-it-be-fixed). nullable: true max_bytes: type: string format: int64 title: >- This sets the maximum size of total evidence in bytes that can be committed in a single block. and should fall comfortably under the max block bytes. Default is 1048576 or 1MB description: >- EvidenceParams determine how we handle evidence of malfeasance. nullable: true additionalProperties: false validator: type: object properties: pub_key_types: type: array items: type: string description: >- ValidatorParams restrict the public key types validators can use. NOTE: uses ABCI pubkey naming, not Amino names. nullable: true additionalProperties: false version: type: object properties: app: type: string format: uint64 description: VersionParams contains the ABCI application version. nullable: true additionalProperties: false abci: type: object properties: vote_extensions_enable_height: type: string format: int64 description: >- vote_extensions_enable_height configures the first height during which vote extensions will be enabled. During this specified height, and for all subsequent heights, precommit messages that do not contain valid extension data will be considered invalid. Prior to this height, vote extensions will not be used or accepted by validators on the network. Once enabled, vote extensions will be created by the application in ExtendVote, passed to the application for validation in VerifyVoteExtension and given to the application to use when proposing a block during PrepareProposal. description: >- ABCIParams configure functionality specific to the Application Blockchain Interface. nullable: true additionalProperties: false authority: type: object properties: authority: type: string nullable: true additionalProperties: false nullable: true additionalProperties: false app_hash: type: string format: byte description: app_hash is the app hash after processing this block. nullable: true description: >- GetLatestBlockResultsResponse is the response type for the Query/GetLatestBlockResults RPC method. additionalProperties: false default: description: An unexpected error response. content: '*/*': schema: type: object properties: code: type: integer format: int32 message: type: string details: type: array items: type: object properties: '@type': type: string description: >- A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in `path/google.protobuf.Duration`). The name should be in a canonical form (e.g., leading "." is not accepted). In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme `http`, `https`, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows: * If no scheme is provided, `https` is assumed. * An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error. * Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.) Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com. As of May 2023, there are no widely used type server implementations and no plans to implement one. Schemes other than `http`, `https` (or the empty scheme) might be used with implementation specific semantics. additionalProperties: {} description: >- `Any` contains an arbitrary serialized protocol buffer message along with a URL that describes the type of the serialized message. Protobuf library provides support to pack/unpack Any values in the form of utility functions or additional generated methods of the Any type. Example 1: Pack and unpack a message in C++. Foo foo = ...; Any any; any.PackFrom(foo); ... if (any.UnpackTo(&foo)) { ... } Example 2: Pack and unpack a message in Java. Foo foo = ...; Any any = Any.pack(foo); ... if (any.is(Foo.class)) { foo = any.unpack(Foo.class); } // or ... if (any.isSameTypeAs(Foo.getDefaultInstance())) { foo = any.unpack(Foo.getDefaultInstance()); } Example 3: Pack and unpack a message in Python. foo = Foo(...) any = Any() any.Pack(foo) ... if any.Is(Foo.DESCRIPTOR): any.Unpack(foo) ... Example 4: Pack and unpack a message in Go foo := &pb.Foo{...} any, err := anypb.New(foo) if err != nil { ... } ... foo := &pb.Foo{} if err := any.UnmarshalTo(foo); err != nil { ... } The pack methods provided by protobuf library will by default use 'type.googleapis.com/full.type.name' as the type URL and the unpack methods only use the fully qualified type name after the last '/' in the type URL, for example "foo.bar.com/x/y.z" will yield type name "y.z". JSON ==== The JSON representation of an `Any` value uses the regular representation of the deserialized, embedded message, with an additional field `@type` which contains the type URL. Example: package google.profile; message Person { string first_name = 1; string last_name = 2; } { "@type": "type.googleapis.com/google.profile.Person", "firstName": , "lastName": } If the embedded message type is well-known and has a custom JSON representation, that representation will be embedded adding a field `value` which holds the custom JSON in addition to the `@type` field. Example (for message [google.protobuf.Duration][]): { "@type": "type.googleapis.com/google.protobuf.Duration", "value": "1.212s" } ````