Skip to content

Question on API tx order for same block & low priority suggestions #165

@ildarmgt

Description

@ildarmgt

Hi, thanks for great API and explorer.

When using /api/address/:address/txs/chain or /block/:hash/txs
is the order API lists tx that were in same block always based on order within that block?

Documentation does mention sorted with newest first but since blocks confirm its tx at same time, I wasn't sure.

I would like to use some logic that depends on placement within the block for tie breaking beyond block_height, and I imagine various embedded protocols could use too.

Requesting possibly the entire block's worth of tx with /block/:hash/txs[/:start_index] would be a lot of redundant info just to find order or to get txid's within a block for merkle proof. Is it possible to find the order of my tx's by txid within same block another way?

I just wanted to get a confirmation on the order used in API but possible suggestions:

  • tx index within a block for transaction format > status - the only missing sorting data point for checking sorting
  • endpoint that has only provides all txid for a block (data you already have) with indexes or specified order in documentation
  • if people want to provide more confidence in api results, is it possible to have an endpoint for only the hashes needed for a specific txid merkle proof to the root in the header?

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions