Transaction's block

[mkpuig]

Hi,
Is there any chance to determine via assets api the main chain's blockheight/blockhash of a transaction?
Getting via /txmeta might return one or more block hashes/heights
Also tried /merkle_proof the transaction and returned the blockHeigh of the orphan block, son can't be used as truth source to determine the "good" block.

The txid ( testnet ) is : ee8095c325dd13d4b6e91be6060328f03af4592cf1c0e98a4420a4639bc7ec8a

Could it be one of ?
1 - /txmeta returns a field indicating which is the main chain blockheight/blockhash
2 - /tx return the transaction data among with main chain blockHeight / blockHash / (blockTime?)

Thank you in advance!

Also merkle proof graphic points to orphaned block

[oskarszoon]

Couple of bugs and an API gap here. Path forward:

1. /merkle_proof returning orphan block — confirmed bug.
util/merkleproof/merkle_proof.go picks BlockIDs[0] with no main-chain filter. For your tx the orphan happens to be index 0. Same problem if a tx is only ever in an orphan block.

Fix: return proof against the main-chain block, or 404 "transaction not in main chain" if none. Tracking in #961.

2. /txmeta missing main-chain indicator — your option 1.
Will add mainChainIndex to the response — single integer pointing at the canonical entry in the parallel arrays, or -1 if tx is orphan-only / mempool. Avoids the per-block round-trip you'd otherwise need. Tracking in #962.

3. /tx/json missing block info — your option 2.
Not planning to add block context to /tx itself. Once #962 ships, /txmeta/{txid}/json is the canonical endpoint for "tx + main-chain block hash/height". /tx stays as raw transaction bytes/JSON.

Workaround until fixes ship: call /txmeta/{txid}/json, then for each blockHashes[i] check /block/{hash}/header (or use the RPC getblock) to find the one on the active chain. Slow but correct.

We also found a related-shape issue in the validator where parent tx height uses BlockHeights[0] for UTXO maturity checks — separate audit issue, doesn't affect you but worth a look. Tracking in #963.