> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.
## Submitting Feedback
If you encounter incorrect, outdated, or confusing documentation on this page, submit feedback:
POST https://docs.chainstack.com/feedback
```json
{
"path": "/reference/fantom-gettransactionbyhash",
"feedback": "Description of the issue"
}
```
Only submit feedback when you have something specific and actionable to report.
# eth_getTransactionByHash | Fantom
Fantom API method that returns information about a transaction from its hash. It is used to retrieve information about a specific transaction by its hash. The method returns an object with details about the transaction, such as the sender, recipient, gas used, transaction value, and more.
**Get your own node endpoint today**
[Start for free](https://console.chainstack.com/) and get your app to production levels immediately. No credit card required.
You can sign up with your GitHub, X, Google, or Microsoft account.
## Parameters
* `hash` — the hash identifying a transaction
## Response
* `object` — the transaction response object, or `null` if no transaction is found:
* `blockHash` — the block hash. Identifies the block in which the transaction was included. This field is `null` for transactions that have not yet been included in a block.
* `blockNumber` — the number of the block in which the transaction was included. This field is `null` for transactions that have not yet been included in a block.
* `from` — the address of the sender who initiated the transaction.
* `gas` — the units of gas included in the transaction by the sender.
* `gasPrice` — the price of gas in Wei included in the transaction by the sender.
* `maxFeePerGas` — the maximum amount the transaction's sender is willing to pay per unit of gas for the transaction to be executed.
* `maxPriorityFeePerGas` — the maximum priority fee the transaction sender is willing to pay per gas unit.
* `hash` — the hash that uniquely identifies the transaction.
* `input` — the optional input data sent with the transaction., usually used to interact with smart contracts.
* `nonce` — a counter identifying the transaction's number sent by the sender wallet; it essentially identifies how many transactions an account has made. It is used to ensure each transaction is executed only once.
* `to` — the recipient's address of the transaction if it was a transaction to an address. For contract creation transactions, this field is `null`.
* `transactionIndex` — the index of the transaction within the block. This field is `null` for transactions that have not yet been included in a block.
* `value` — the value of the native token transferred along with the transaction in Wei.
* `type` — the [type](https://ethereum.org/en/developers/docs/transactions/#types-of-transactions) of the transaction. `0` indicates a regular transfer; `2` indicates a contract creation or smart contract function call.
* `accessList` — a list of [authorized addresses and storage keys](https://eips.ethereum.org/EIPS/eip-2930#:~:text=The%20accessList%20specifies%20a%20list,of%20accessing%20outside%20the%20list.) the transaction plans to interact with.
* `v` — the recovery parameter in the [Ethereum Signature Algorithm](https://ethereum.org/en/glossary/#ecdsa) (ECDSA).
* `r` — the first component of the signature in the [Ethereum Signature Algorithm](https://ethereum.org/en/glossary/#ecdsa) (ECDSA).
* `s` — the second component of the signature in the [Ethereum Signature Algorithm](https://ethereum.org/en/glossary/#ecdsa) (ECDSA).
## `eth_getTransactionByHash` code examples
```javascript web3.js theme={"system"}
const { Web3 } = require("web3");
const NODE_URL = "CHAINSTACK_NODE_URL";
const web3 = new Web3(NODE_URL);
async function getTransaction(transactionHash) {
const transaction = await web3.eth.getTransaction(transactionHash)
console.log(transaction)
}
getTransaction("0x658d83eb9395221ffb8c2bf3696b88f61262527b145bd7ffdb7310edb8886e3b")
```
```javascript ethers.js theme={"system"}
const ethers = require('ethers');
const NODE_URL = "CHAINSTACK_NODE_URL";
const provider = new ethers.JsonRpcProvider(NODE_URL);
const getTransaction = async (transactionHash) => {
const transaction = await provider.send("eth_getTransactionByHash", [transactionHash]);
console.log(transaction);
};
getTransaction("0x658d83eb9395221ffb8c2bf3696b88f61262527b145bd7ffdb7310edb8886e3b")
```
```python web3.py theme={"system"}
from web3 import Web3
node_url = "CHAINSTACK_NODE_URL"
web3 = Web3(Web3.HTTPProvider(node_url))
print(web3.eth.get_transaction("0x658d83eb9395221ffb8c2bf3696b88f61262527b145bd7ffdb7310edb8886e3b"))
```
## Use case
One use case for `eth_getTransactionByHash` is to inspect a specific transaction and display information about it, such as the address sent, the block it was included in, and the number of transactions the sender sent so far (nonce). This information can be useful for monitoring and analyzing transactions.
## OpenAPI
````yaml /openapi/fantom_node_api/eth_getTransactionByHash.json POST /4ab982aa70a7baead515ffdb5915df3f
openapi: 3.0.0
info:
title: Fantom Node API
version: 1.0.0
description: This is an API for interacting with a Fantom node.
servers:
- url: https://fantom-mainnet.core.chainstack.com
security: []
paths:
/4ab982aa70a7baead515ffdb5915df3f:
post:
tags:
- Transactions info
summary: eth_getTransactionByHash
operationId: getTransactionByHash
requestBody:
required: true
content:
application/json:
schema:
type: object
properties:
id:
type: integer
default: 1
jsonrpc:
type: string
default: '2.0'
method:
type: string
default: eth_getTransactionByHash
params:
type: array
items:
type: string
title: Transaction hash
default:
- >-
0x58e61f99a15aa3cd76162037225287a574d9eda91d2a9d35ff0fcde1cccda4a0
responses:
'200':
description: The transaction information
content:
application/json:
schema:
type: object
properties:
jsonrpc:
type: string
id:
type: integer
result:
type: object
````