List Confirmed Transactions By Address And Time Range
This endpoint will list confirmed transactions by the attribute address
and the query parameters fromTimestamp
and toTimestamp
which gives customers the opportunity to filter the results by a specified time period.
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.
-
Requiredaddress string
Represents the public address, which is a compressed and shortened form of a public key.
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. -
RequiredfromTimestamp integer
Defines the specific time/date from which the results will start being listed.
-
Optionallimit integer
Defines how many items should be returned in the response per page basis.
-
Optionaloffset integer
The starting index of the response items, i.e. where the response should start listing the returned items.
-
RequiredtoTimestamp integer
Defines the specific time/date to which the results will be listed.
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 : 2021-03-20 -
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
-
Requiredlimit integer
Defines how many items should be returned in the response per page basis.
Example : 50 -
Requiredoffset integer
The starting index of the response items, i.e. where the response should start listing the returned items.
Example : 0 -
Requiredtotal integer
Defines the total number of items returned in the response.
Example : 100 -
Requireditems arrayExample : Array ( )
-
Requiredindex integer
Represents the index position of the transaction in the block.
Example : 1 -
OptionalminedInBlockHash 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 -
OptionalminedInBlockHeight 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 : 1903849 -
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 protocolshash
is different fromtransactionId
for SegWit transactions.Example : 1ec73b0f61359927d02376b35993b756b1097cb9a857bec23da4c98c4977d2b2 -
RequiredtransactionId string
Represents the unique identifier of a transaction, i.e. it could be
transactionId
in UTXO-based protocols like Bitcoin, and transactionhash
in Ethereum blockchain.Example : 4b66461bf88b61e1e4326356534c135129defb504c7acb2fd6c92697d79eb250 -
Requiredfee object
-
Requiredamount string
Defines the amount of the transaction fee.
Example : 0.00016932 -
Requiredunit string
Defines the specific unit of the fee.
Example : BTC
-
-
RequiredblockchainSpecific object One Ofobject
-
Requiredlocktime integer
Represents the locktime on the transaction on the specific blockchain, i.e. the blockheight at which the transaction is valid.
Example : 1781965 -
Requiredsize integer
Represents the total size of this transaction.
Example : 125 -
RequiredvSize integer
Defines the transaction's virtual size.
Example : 166 -
Requiredversion integer
Defines the version of the transaction.
Example : 2 -
Requiredvin array
Represents the transaction inputs.
-
Requiredaddresses array
Represents the addresses which send/receive the amount.
Example : 2N5PcdirZUzKF9bWuGdugNuzcQrCbBudxv1 -
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 : 0014daaf6d5cb86befe42df851a4d1df052e663754c1 -
Requiredhex string
Represents the hex of the public key of the address.
Example : 160014daaf6d5cb86befe42df851a4d1df052e663754c1 -
Requiredtype string
Represents the script type of the reference transaction identifier.
Example : scripthash
-
-
Requiredsequence string
Represents the script sequence number.
Example : 4294967295 -
Optionaltxid string
Represents the reference transaction identifier.
Example : caee978cae255bbe303ac86152679e46113a8b12925aa3afaa312d89d11ccbf8 -
Optionaltxinwitness array
Represents an array hex-encoded witness data (if there is any) as strings.
Example : 3045022100c11ea5740bcd69f0f68a4914279838014d28923134d18e05c5a5486dfd06cc8c02200dadccec3f07bed0d1040f9e5a155efa5fdd40fc91f92342578d26848da4c6b901 -
Optionalvalue string
Represents the sent/received amount.
Example : 0.00873472 -
Optionalvout integer
Defines the vout of the transaction output, i.e. which output to spend.
Example : 1
-
-
Requiredvout array
Represents the transaction outputs.
-
RequiredisSpent boolean
Defines whether the output is spent or not.
Example : True -
RequiredscriptPubKey object
Represents the script public key.
-
Requiredaddresses array
Represents the addresses which send the amount.
Example : 2N5PcdirZUzKF9bWuGdugNuzcQrCbBudxv1 -
Requiredasm string
Represents the assembly of the script public key of the address.
Example : OP_HASH160 ca94af32587de4e5006685ffffc65a818ccd3fbc OP_EQUAL -
Requiredhex string
Represents the hex of the script public key of the address.
Example : a914507a5bd8cac1d9efdf4c0a4bfacb3e0abb4f8d1587 -
OptionalreqSigs integer
Represents the required signatures.
Example : 1 -
Requiredtype string
Represents the script type.
Example : scripthash
-
-
Requiredvalue string
Represents the sent/received amount.
Example : 0.000144
-
-
-
-