Get Transaction Details By Transaction ID From Callback
This endpoint creates a shortcut to obtain information from Blockchain data by going through Blockchain Events and a specific Event Subscription. It provides data for a specific transaction from the Event it takes part in by providing the transactionId
attribute. It applies only for Events related to that user.
Path Parameters
-
Requiredblockchain string
Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
-
Requirednetwork string
Represents the name of the blockchain network used; blockchain networks are usually identical as technology and software, but they differ in data, e.g. - "mainnet" is the live network with actual data while networks like "testnet", "ropsten" are test networks.
-
RequiredtransactionId string
Represents the unique identifier of a transaction, i.e. it could be transactionId in UTXO-based protocols like Bitcoin, and transaction hash in Ethereum blockchain.
Query parameters
-
Optionalcontext string
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error.
context
is specified by the user.
Response schema
Content-Type: application/json
The request has been successful.
Object :
-
RequiredapiVersion string
Specifies the version of the API that incorporates this endpoint.
Example : 2023-04-25 -
RequiredrequestId string
Defines the ID of the request. The
requestId
is generated by Crypto APIs and it's unique for every request.Example : 601c1710034ed6d407996b30 -
Optionalcontext string
In batch situations the user can use the context to correlate responses with requests. This property is present regardless of whether the response was successful or returned as an error.
context
is specified by the user.Example : yourExampleString -
Requireddata object
-
Requireditem object
-
Requiredindex integer
Represents the index position of the transaction in the specific block.
Example : 1 -
RequiredisConfirmed boolean
Represents the state of the transaction whether it is confirmed or not confirmed.
Example : True -
RequiredminedInBlockHash string
Represents the hash of the block where this transaction was mined/confirmed for first time. The hash is defined as a cryptographic digital fingerprint made by hashing the block header twice through the SHA256 algorithm.
Example : 00000000407f119ecb74b44229228910400aaeb9f4e3b9869955b85a53e9b7db -
RequiredminedInBlockHeight integer
Represents the hight of the block where this transaction was mined/confirmed for first time. The height is defined as the number of blocks in the blockchain preceding this specific block.
Example : 1939750 -
Requiredrecipients array
Represents a list of recipient addresses with the respective amounts. In account-based protocols like Ethereum there is only one address in this list.
-
Requiredaddress string
The address which receives this transaction. In UTXO-based protocols like Bitcoin there could be several senders while in account-based protocols like Ethereum there is always only one recipient.
Example : 2MzakdGTEp8SMWEHKwKM4HYv6uNCBXtHpkV -
Requiredamount string
Represents the amount received to this address.
Example : 0.000144
-
-
Requiredsenders array
Represents a list of sender addresses with the respective amounts. In account-based protocols like Ethereum there is only one address in this list.
-
Requiredaddress string
Represents the address which sends this transaction. In UTXO-based protocols like Bitcoin there could be several senders while in account-based protocols like Ethereum there is always only one sender.
Example : 2N5PcdirZUzKF9bWuGdugNuzcQrCbBudxv1 -
Requiredamount string
Represents the total amount sent by this address including the fee.
Example : 0.00873472
-
-
Requiredtimestamp integer
Defines the exact date/time in Unix Timestamp when this transaction was mined, confirmed or first seen in Mempool, if it is unconfirmed.
Example : 1582202940 -
RequiredtransactionHash string
Represents the same as transactionId for account-based protocols like Ethereum, while it could be different in UTXO-based protocols like Bitcoin. E.g., in UTXO-based protocols hash is different from transactionId for SegWit transactions.
Example : 1ec73b0f61359927d02376b35993b756b1097cb9a857bec23da4c98c4977d2b2 -
Requiredfee object
-
Requiredamount string
When isConfirmed is True - Defines the amount of the transaction fee When isConfirmed is False - For ETH-based blockchains this attribute represents the max fee value.
Example : 0.00000300 -
Requiredunit string
Defines the unit of the fee.
Example : BTC
-
-
RequiredtransactionId string
String representation of the transaction hash
-
RequiredblockchainSpecific object One Ofobject
-
Requiredlocktime integer
Represents the time at which a particular transaction can be added to the blockchain.
Example : 0 -
Requiredsize integer
Represents the total size of this transaction.
Example : 223 -
RequiredvSize integer
Represents the virtual size of this transaction.
Example : 223 -
Requiredversion integer
Represents the transaction version number.
Example : 2 -
Requiredvin array
Represents the transaction inputs.
-
Requiredaddresses array
2N5PcdirZUzKF9bWuGdugNuzcQrCbBudxv1
Example : mtFYoSowT3i649wnBDYjCjewenh8AuofQb -
Optionalcoinbase string
Represents the coinbase hex.
Example : 0399991d20706f6f6c2e656e6a6f79626f646965732e636f6d20393963336532346234374747a53e994c4a000001 -
RequiredscriptSig object
Specifies the required signatures.
-
Requiredasm string
The asm strands for assembly, which is the symbolic representation of the Bitcoin's Script language op-codes.
Example : 304402202eb16569b2c1f5898c1ab5b23d41e0783ae37943bc6745784fb810f955deafbd02203562872c3a3c7c2423a752f27ba6ae01e66ffc56fe8e463a90498dd5659f8d90 -
Requiredhex string
Represents the hex of the public key of the address.
Example : 47304402202eb16569b2c1f5898c1ab5b23d41e0783ae37943bc6745784fb810f955deafbd02203562872c3a3c7c2423a752f27ba6ae01e66ffc56fe8e463a90498dd5659f8d90012102275753690ab58df3c923001e94d407e30b03e60b1f2461729a1dd4f37ebe2469 -
Requiredtype string
Represents the script type of the reference transaction identifier.
Example : pubkeyhash
-
-
Requiredsequence integer
Represents the script sequence number.
Example : 4294967295 -
Optionaltxid string
Represents the reference transaction identifier.
Example : fd572c11a7e3eb39251746a9b2f4f53d5218b7cd0fb6e82ba48e678211d677c9 -
Requiredtxinwitness array
Represents an array hex-encoded witness data (if there is any) as strings.
Example : mtFYoSowT3i649wnBDYjCjewenh8AuofQb -
Optionalvalue string
Represents the sent/received amount.
Example : 0.00002 -
Optionalvout integer
It refers to the index of the output address of this transaction. The index starts from 0.
Example : 1
-
-
Requiredvout array
Represents the transaction outputs.
-
RequiredisSpent boolean
Defines whether the output is spent or not.
Example : False -
RequiredscriptPubKey object
Represents the script public key.
-
Requiredaddresses array
Represents the addresses which send the amount.
Example : 2MzakdGTEp8SMWEHKwKM4HYv6uNCBXtHpkV -
Requiredasm string
Represents the assembly of the script public key of the address.
Example : OP_HASH160 507a5bd8cac1d9efdf4c0a4bfacb3e0abb4f8d15 OP_EQUAL -
Requiredhex string
Represents the hex of the script public key of the address.
Example : a914507a5bd8cac1d9efdf4c0a4bfacb3e0abb4f8d1587 -
RequiredreqSigs integer
Represents the required signatures.
Example : 1 -
Requiredtype string
Represents the script type.
Example : scripthash
-
-
Requiredvalue string
Represents the sent/received amount.
Example : 0.00014400
-
-
-
-