List Omni Transactions By Block Height
This endpoint will list Omni transactions by an attribute blockHeight
. The transactions listed will detail additional information such as hash, addresses, time of creation in Unix timestamp, etc.
Path Parameters
-
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.
-
Requiredblockchain string
Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
-
RequiredblockHeight string
Represents the number of blocks in the blockchain preceding this specific block. Block numbers have no gaps. A blockchain usually starts with block 0 called the "Genesis block".
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. -
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.
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 : 2.0.0 -
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 ( )
-
Requiredamount string
Defines the amount of the sent tokens.
Example : 798.483157 -
Requireddivisible boolean
Defines whether the attribute can be divisible or not, as boolean. E.g., if it is "true", the attribute is divisible.
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 : 000000000000000000061610767eaa0394cab83c70ff1c09dd6b2a2bdad5d1d1 -
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 : 59000 -
RequiredpositionInBlock integer
Represents the index position of the transaction in the specific block.
Example : 18 -
RequiredpropertyId integer
Represents the identifier of the tokens to send.
Example : 2 -
Requiredrecipients array
Represents an object of addresses that receive the transactions.
Example : ms4KNsbNpoU8g424pzmEjbkFbfAHae1msB-
Requiredaddress string
Represents the hash of the address that receives the funds.
Example : 3Ld5yZ4fqTrW44cUGxpjEuBwAEtCsYUP28 -
Requiredamount string
Defines the amount of the received funds as a string.
Example : 0.1
-
-
Requiredsenders array
Represents an object of addresses that provide the funds.
-
Requiredaddress string
Represents the hash of the address that provides the funds.
Example : 1MRyVg2dyZNEFDy8G6i1hNcerkeZiXYK4S -
Requiredamount string
Represents the total amount sent by this address including the fee.
Example : 0.1
-
-
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 : 1565743888 -
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 : f43ecd605d8d733d02684c17c3a61d66aed7a9ec4c627fb060b763c348696259 -
Requiredtype string
Defines the type of the transaction as a string.
Example : Simple Send -
RequiredtypeInt integer
Defines the type of the transaction as a number.
Example : 0 -
Requiredvalid boolean
Defines whether the transaction is valid or not, as boolean. E.g., if it is "true", the transaction is valid.
Example : True -
Requiredversion integer
Defines the specific version.
Example : 0 -
Requiredfee object
-
Requiredamount string
Defines the amount of the fee.
Example : 0.0007 -
Requiredunit string
Defines the unit of the fee.
Example : BTC
-
-
-