Response payload

Each response carries a chain-specific block in a protobuf Any, a fork step and an opaque cursor. Decode EVM blocks with sf.ethereum.type.v2.Block. Extended endpoints include calls and state changes as well as transactions and receipts.

1{
2  "step": "STEP_NEW",
3  "cursor": "<opaque cursor returned by the server>",
4  "block": {
5    "@type": "type.googleapis.com/sf.ethereum.type.v2.Block",
6    "number": "25983910",
7    "transaction_traces": [
8      {
9        "receipt": {
10          "logs": [
11            {
12              "address": "oLhpkcYhizbB0Z1KLp6wzjYG60g=",
13              "topics": [
14                "3fJSrRviyJtpwrBo/DeNqpUrp/FjxKEWKPVaTfUjs+8=",
15                "AAAAAAAAAAAAAAAAERERERERERERERERERERERERERE=",
16                "AAAAAAAAAAAAAAAAIiIiIiIiIiIiIiIiIiIiIiIiIiI="
17              ],
18              "data": "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAPQkA="
19            }
20          ]
21        }
22      }
23    ]
24  }
25}

The example shows one USDC Transfer log. Hashes, headers and other transaction fields are omitted for readability. Full and filtered streams use the same block schema; filtering removes transactions that do not match. Try It displays actual responses and lets you export them.

EVM block, transaction & log schema