Web3.py – Python getBlock(full_transactions=True) Return Value Explained

pythonweb3.py

I am trying to get the meaning of all fields returned by getBlock, but no where to find!

web3.eth.getBlock(block_identifier='pending', full_transactions=True)

returns a list of :

AttributeDict({'blockHash': HexBytes('0x50edaaa071801750cb71d5b89b23a98e4ac911a3451acfa1646ee45a45200902'),
   'blockNumber': 11633063,
   'from': '0xA2F4442B71267F12A6844bb9b93cb744F0217baF',
   'gas': 243390,
   'gasPrice': 132000000000,
   'hash': HexBytes('0x630a3fc021744bb400437578464b4c4f3eeea82b3e1f58d3a2483e2cb0fbe9e1'),
   'input': '0x1e83409a000000000000000000000000a2f4442b71267f12a6844bb9b93cb744f0217baf',
   'nonce': 4,
   'r': HexBytes('0x02c77d2251fbd4b97aa0285e7b7651ff7775b8d41f3c5c42925a30ae087a6fdb'),
   's': HexBytes('0x4e8c0bb1e73ed38dc02a3a22167507b2572e1a18440a054ac421f2342f8b6fd9'),
   'to': '0x098e1708b920EFBdD7afe33Adb6a4CBa30c370B9',
   'transactionIndex': 87,
   'v': 28,
   'value': 0})

Could anyone provide some explanation of those fields (especially input, r, s and v).

Thank you!

Best Answer

Looks like full_transactions returns a list of multiple getTransactionByHash call results.

You can find the description of Ethereum JSON-RPC API fields here:

https://eth.wiki/json-rpc/API

Related Solutions

[Ethereum] Convert String to Bytes32 Web3.py v4.3 Python

Simply data.encode('utf-8') should be sufficient, if you are converting a string to bytes data.

If your string is more than 32 bytes long after encoding to UTF-8, then your problem is that your contract can't accept the data you want to send.

More background

If a function takes a bytes32, it cannot accept a value longer than 32 bytes. Web3.py will actually reject the function as a possibility based on the type mismatch (because multiple functions with the same name and different types are allowed).

If you have more than 32 bytes to send in, you probably don't want to blindly clip off the end. What you need to do will be highly dependent on the semantics of the contract that you are interacting with.

You do not need to pad the value, Web3.py will handle that for you.

Finally, bytes(str_data, 'utf-8') is equivalent to str_data.encode('utf-8'). Which you prefer is a matter of taste, I suppose, and potentially performance.

[Ethereum] web3 python sendTransaction error

The etherscan API is not a JSON-RPC-compatible API. If you want to use a remote node with web3, you can use something like Infura.

According to their documentation, there are ways to invoke the JSON-RPC methods, but they don't actually implement the API externally. For example, to get the latest block number in the JSON-RPC API, you would send a POST like this:

curl -X POST --data '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":83}' localhost:8545

(which web3.py does for you behind the scenes of w3.eth.blockNumber)

In the etherscan API, you would send a GET, like this:

curl https://api.etherscan.io/api?module=proxy&action=eth_blockNumber&apikey=YourApiKeyToken

The two APIs are simply different. It would be possible to create a new specialized EtherscanProvider to work inside web3.py, instead of the normal HTTPProvider, but it would take a bit of work.

Best Answer

Related Solutions

[Ethereum] Convert String to Bytes32 Web3.py v4.3 Python

[Ethereum] web3 python sendTransaction error

Related Topic