A blockchain transaction is a transfer of value or data from one participant to another within a blockchain network. In a blockchain, transactions are stored in blocks, which are connected in a linear, chronological chain, hence the name "blockchain".
When a transaction occurs on a blockchain, it is first broadcast to the network, where it is verified and validated by the nodes or computers that participate in the network. Once a consensus is reached among the nodes, the transaction is recorded in a block, which is then added to the blockchain.
A typical blockchain transaction contains the following information:
Sender address: The address of the participant who initiates the transaction.
Recipient address: The address of the participant who receives the transaction.
Amount: The value or quantity of the asset or data being transferred.
Transaction fee: The fee paid by the sender to incentivize the network to process the transaction.
Timestamp: The date and time when the transaction occurred.
Transaction hash: A unique identifier that is generated for each transactions.
Amberdata provides extensive data within the transactions endpoints including all the sending and receiving addresses (including token transfers), fees (gas), amounts, op codes, block number and block hash, timestamps and so much more. The great thing about our transactions endpoints is that we give you the choice of how granular you want to query the data. From the transaction hash level, to the address level up to the block level, Amberdata allows you to decide how much data you need. We commonly say that our transaction endpoints can provide everything you need in a single query as opposed to using multiple tools and digging through menus and sub-menus to find the right data.
The Transactions endpoints found throughout the different On-Chain namespaces are available via REST API, WebSockets or JSON RPC. The list of supported Blockchain networks can be found in the API Documentation here.
Since we maintain our own nodes, we have every event from the genesis block forward which enables us to provide complete historical datasets for most of the chains we support.
What is the main benefit of your granular transaction data?
- Depending on the application, having block, address or tx hash level transaction data could be useful for research/back-testing, accounting or a tax use case, and more.
What kinds of transaction data is returned in the API response?
- The response will show all of the addresses involved in the transaction, gas prices and gas used, transaction hash, nonce, # of confirmations, timestamp and much more.
Updated 10 months ago