Transactions
Like blocks, transactions have no dedicated Core page: search hands a transaction id to an external block explorer. What Core does own is the transaction data behind every figure it shows, and the safety rules around transactions it helps you build.
Reading a transaction
Section titled “Reading a transaction”The public facade serves the full transaction, including previous outputs, so a caller can compute a fee and see what each input was worth without a second round trip.
curl -s https://api.bitcoinuniverse.io/mempool/api/tx/<txid>The response carries txid, version, locktime, size, weight, fee,
vin, vout, and status. Each vin includes its prevout, and status
carries confirmed, block_hash, block_height, and block_time. The full
shape is in the OpenAPI reference.
Searching an outpoint
Section titled “Searching an outpoint”An outpoint, <txid>:<vout>, is recognised exactly. It resolves to that
specific output of that transaction, labelled “Output n of txid”. Outpoints
matter more than transaction ids in this product, because a metaprotocol asset
lives at an outpoint, not at an address, and several outputs created by one
transaction are separate assets with separate histories.
That separation is preserved throughout: Portfolio and the sell lists key on the full outpoint, so several outputs from one transaction stay distinct and keep their own entered prices, and a batch settlement that shares one Bitcoin transaction still produces distinct activity rows per trade.
Broadcasting
Section titled “Broadcasting”A transaction broadcast is submitted once. If the network response is uncertain, Core checks whether the transaction is already visible before returning success. It does not blindly send the same transaction to a second provider, and there is no public-provider fallback to send it to.
Once broadcast, a transaction cannot be recalled. Every Core review screen says so before the wallet prompt, and transaction safety covers what to check first.
Transactions in activity
Section titled “Transactions in activity”Activity rows are dated from when the event happened, not from when a record was last written. Maintenance passes re-check historical trades, and those passes never move a row’s date forward or resurface an old trade as current activity.
Read the date before treating a row as a signal. Recent activity is a record of past trades. It is not a price feed, a measure of current liquidity, or a prediction. A quiet market shows older dates rather than hiding them.
Confirmation is not settlement
Section titled “Confirmation is not settlement”A confirmed transaction is necessary for a settlement and rarely sufficient. Most protocols also require the protocol-level state transition that transaction was supposed to cause, observed at a stable index checkpoint. A settlement can therefore stay pending after a block: the chain agreed, and the index has not caught up.
Confirmation and reorg policy gives the per-protocol rule.