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

GetBlockByNum2 - Tron

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

This method returns a block by its height, including its header and transactions.

Service

This method is served by the protocol.Wallet and protocol.WalletSolidity service.

This is a read method. It is also served by protocol.WalletSolidity, which returns only confirmed, irreversible data. Use the Solidity service for balance and payment verification.

Method

rpc GetBlockByNum2 (NumberMessage) returns (BlockExtention)

Request Message

NumberMessage

Field
Type
Description

num

int64

The block height to retrieve

Request

grpcurl -H 'x-api-key: <ACCESS-TOKEN>' \
  -d '{"num": 68000000}' \
  go.getblock.io:443 protocol.Wallet/GetBlockByNum2
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.GetBlockByNum2(api_pb2.NumberMessage(num=68000000), 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.GetBlockByNum2(ctx, &api.NumberMessage{Num: 68000000})
fmt.Println(resp)

Response Message

BlockExtention

Field
Type
Description

blockid

bytes

The block hash

block_header

BlockHeader

The block header with number and timestamp

transactions

repeated TransactionExtention

Transactions in the block

Use Cases

  • Block Explorers: Render a block by height

  • Chain Indexing: Stream blocks by height into a store

  • USDT Tracking: Scan a block for TRC-20 transfers

  • Confirmation Context: Read a block's time and producer

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?