Quote from: mtbitcoin on October 04, 2014, 02:59:36 PM

Quote from: PhantomPhreak on October 04, 2014, 02:30:08 PM

Quote from: mtbitcoin on October 04, 2014, 01:18:14 PM

Quote from: CounterpartyRippler on October 04, 2014, 11:59:11 AM

Can you add the field "match_expire_index" from https://github.com/CounterpartyXCP/counterpartyd/blob/master/lib/blocks.py#L318 to table on http://www.blockscan.com/order_match.aspx?

Because it's not easy to figure out when one's order was matched.

Is the match_expire_index used to used to designate the block index when the order was matched?

It's used to designate the block at which an order match will expire.

That was what I thought so too... Having said that, how would suggest that we determine the block that an order matches?

Can this be done by looking at the larger value of either the tx0_index or tx1_index ?

The order matches table has a column block_index. (Because of re-matches, the larger tx_index value isn't reliable.)