For the complete documentation index, see llms.txt. This page is also available as Markdown.

GetBlockByLimitNext2 - Tron

Example code for the GetBlockByLimitNext2 gRPC method. Complete guide on how to use GetBlockByLimitNext2 gRPC method in GetBlock Web3 documentation.

This method returns a range of blocks between a start height (inclusive) and an end height (exclusive) in one call.

Service

This method is served by the protocol.Wallet service.

Method

rpc GetBlockByLimitNext2 (BlockLimit) returns (BlockListExtention)

Request Message

BlockLimit

Field
Type
Description

startNum

int64

First block height in the range, inclusive

endNum

int64

End block height, exclusive

Request

grpcurl -H 'x-api-key: <ACCESS-TOKEN>' \
  -d '{"startNum": 68000000, "endNum": 68000005}' \
  go.getblock.io:443 protocol.Wallet/GetBlockByLimitNext2
example.py
import grpc
# Stubs generated from java-tron's api.proto with grpcio-tools
from api import api_pb2_grpc
from core import Contract_pb2, Tron_pb2

creds = grpc.ssl_channel_credentials()
channel = grpc.secure_channel('go.getblock.io:443', creds)
metadata = [('x-api-key', '<ACCESS-TOKEN>')]
stub = api_pb2_grpc.WalletStub(channel)

response = stub.GetBlockByLimitNext2(api_pb2.BlockLimit(startNum=68000000, endNum=68000005), metadata=metadata)
print(response)
example.go
conn, _ := grpc.Dial(
    "go.getblock.io:443",
    grpc.WithTransportCredentials(credentials.NewTLS(&tls.Config{})),
)
defer conn.Close()

client := api.NewWalletClient(conn)
ctx := metadata.AppendToOutgoingContext(
    context.Background(), "x-api-key", "<ACCESS-TOKEN>")

resp, _ := client.GetBlockByLimitNext2(ctx, &api.BlockLimit{StartNum: 68000000, EndNum: 68000005})
fmt.Println(resp)

Response Message

BlockListExtention

Field
Type
Description

block

repeated BlockExtention

Blocks in the requested range

Use Cases

  • Batch Indexing: Fetch a window of blocks in one request

  • Backfill: Catch up a store over a range of heights

  • Analytics: Read a contiguous span of blocks

  • Reorg Windows: Re-scan a recent range after a rollback

Error Handling

Code
Status
Description

3

INVALID_ARGUMENT

A request field is missing or malformed

5

NOT_FOUND

The requested account, block, or transaction does not exist

16

UNAUTHENTICATED

The access token is missing or invalid

13

INTERNAL

The node failed to process the request

Was this helpful?