Get Unconfirmed Omni Transaction By Transaction ID (Txid)
Through this endpoint customers can obtain information on unconfirmed Omni transactions by an attribute transactionId
. The transaction can have information such as hash, height, time of creation in Unix timestamp, etc.
Unconfirmed transactions are usually put in the Mempool and await verification so that they can be added to a block.
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", "rinkeby" are test networks.
-
Requiredblockchain string
Represents the specific blockchain protocol name, e.g. Ethereum, Bitcoin, etc.
-
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.
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 -
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 : You can add any text here -
Requireddata object
-
Requireditem object
-
Requiredamount string
Defines the amount of the sent tokens.
Example : 14.915785 -
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 -
Requiredmined boolean
Defines whether the transaction has been mined or not, as boolean. E.g. if set to "true", it means the transaction is mined.
Example : True -
RequiredpropertyId integer
Represents the identifier of the tokens to send.
Example : 2 -
Requiredrecipients array
Represents an object of addresses that receive the transactions.
-
Requiredaddress string
Represents the hash of the address that receives the funds.
Example : mpBjRU6F2YrgWwxtMw4Fp1hikqPdrx6spB -
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 : ms4KNsbNpoU8g424pzmEjbkFbfAHae1msB -
Requiredamount string
Defines the amount of the sent funds as a string.
Example : 0.1
-
-
Requiredsent boolean
Defines whether the transaction has been sent or not, as boolean. E.g. if set to "true", it means the transaction is sent.
Example : False -
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 : 1616431490 -
RequiredtransactionId string
String representation of the transaction identifier (txid)
Example : 92f17d3d16a1baf7de570a86179cc263cb9866c66778feec2dce111430f41c08 -
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 -
Requiredversion integer
Defines the specific version.
Example : 0 -
Requiredfee object
-
Requiredamount string
Defines the amount of the fee.
Example : 0.0001 -
Requiredunit string
Defines the unit of the fee.
Example : BTC
-
-
-