[BlockScan] Counterparty (XCP) Block Explorer

[Muhammed Zakir]

I have 741 SJCX but in explorer it is showing very low. Do you know why? My SJCX address : 12ZcxUGVoFNw6rhBQ7FfXAjLS1QWE7vJWA. BTW nice work. Good UI.

  ~~MZ~~

[1714796471]

1714796471

[1714796471]

1714796471

[1714796471]

1714796471

[1714796471]

1714796471

[1714796471]

1714796471

[mtbitcoin]

I have 741 SJCX but in explorer it is showing very low. Do you know why? My SJCX address : 12ZcxUGVoFNw6rhBQ7FfXAjLS1QWE7vJWA. BTW nice work. Good UI.

  ~~MZ~~

You had 741. But they were transferred out to the following http://www.blockscan.com/address.aspx?q=19VQq8uW9xYNgK5v9tUuQ9C28k1LpGX6Z4

Are you sure you they still show up in counterwallet ? Private keys secured?

[mtbitcoin]

copied from: https://forums.counterparty.co/index.php/topic,599.msg3383/topicseen.html#msg3383

don't dividends get listed as transactions in the blockscan block explorer?

This is a question better posed for the official XCP forums :-)

However, I will try to answer. There are no individual transactions for the assets delivered via a dividend issuance. There is single one 'main' dividend transaction instruction with specific rules as to how to issue the dividends to the individual addresses . CounterpartyD then receives this instruction and performs the issuance behind the scenes. Each individual CounterpartyD client also does the same and you then have consensus by protocol

cheers

[wellerco]

@mtbitcoin

Some folks at Storj are requesting a public way to show the current (last traded) DEX prices.  I think it would be good for other tokens traded on the DEX as well.

Ideally we'd have a public API for this too.

Would you be willing to update this API call:

http://xcp.blockscan.com/api2.aspx?module=price&asset1=BTC&asset2=XCP

to support all tokens.  So this kind of a call would work as well:

http://xcp.blockscan.com/api2.aspx?module=price&asset1=BTC&asset2=LTBCOIN


Thanks.

[mtbitcoin]

@mtbitcoin

Some folks at Storj are requesting a public way to show the current (last traded) DEX prices.  I think it would be good for other tokens traded on the DEX as well.

Ideally we'd have a public API for this too.

Would you be willing to update this API call:

http://xcp.blockscan.com/api2.aspx?module=price&asset1=BTC&asset2=XCP

to support all tokens.  So this kind of a call would work as well:

http://xcp.blockscan.com/api2.aspx?module=price&asset1=BTC&asset2=LTBCOIN


Thanks.

Sure, that makes sense. And the API would be a good fit for that.

I will look into that as soon as I finish up some of the other changes that I have been working on recently

Cheers

[wellerco]

It looks like CoinMarketCap just integrated the Counterparty DEX.  I wonder how they did that.

http://coinmarketcap.com/exchanges/counterparty-dex/
http://coinmarketcap.com/assets/ltbcoin/#markets

[mtbitcoin]

It looks like CoinMarketCap just integrated the Counterparty DEX.  I wonder how they did that.

http://coinmarketcap.com/exchanges/counterparty-dex/
http://coinmarketcap.com/assets/ltbcoin/#markets

If you run and have access to the CLI, you can do anything

[prophetx]

this address should show about 126 XCP, but the site is showing 0

1MJcVAJ5D2poJovBvdEZt3PpdcR8YY5vMQ

when I input it into counterwallet.co it shows up with the 126 XCP

[mtbitcoin]

this address should show about 126 XCP, but the site is showing 0

1MJcVAJ5D2poJovBvdEZt3PpdcR8YY5vMQ

when I input it into counterwallet.co it shows up with the 126 XCP

The daemon went down so we were backed up a bit. After restarting it we're up to date

You can check the main page to see which are the last block processed, if its not up to date it most likely means the daemon is down

[prophetx]

this address should show about 126 XCP, but the site is showing 0

1MJcVAJ5D2poJovBvdEZt3PpdcR8YY5vMQ

when I input it into counterwallet.co it shows up with the 126 XCP

The daemon went down so we were backed up a bit. After restarting it we're up to date

You can check the main page to see which are the last block processed, if its not up to date it most likely means the daemon is down

i see it now, thanks

[mtbitcoin]

@mtbitcoin

Some folks at Storj are requesting a public way to show the current (last traded) DEX prices.  I think it would be good for other tokens traded on the DEX as well.

Ideally we'd have a public API for this too.

Would you be willing to update this API call:

http://xcp.blockscan.com/api2.aspx?module=price&asset1=BTC&asset2=XCP

to support all tokens.  So this kind of a call would work as well:

http://xcp.blockscan.com/api2.aspx?module=price&asset1=BTC&asset2=LTBCOIN


Thanks.

Ok. Completed as per above. You can now get the both the latest DEX prices for a BTCPAY & NonBTCPay asset pairs.

The code for the NonBTCPay assets pair is still new so it's under testing. Do let me know if you see anything out of place

ex:

http://xcp.blockscan.com/api2.aspx?module=price&asset1=BTC&asset2=SJCX

http://xcp.blockscan.com/api2.aspx?module=price&asset1=SJCX&asset2=XCP
http://xcp.blockscan.com/api2.aspx?module=price&asset1=XCP&asset2=SJCX


Cheers

[wellerco]

Ok. Completed as per above. You can now get the both the latest DEX prices for a BTCPAY & NonBTCPay asset pairs.

The code for the NonBTCPay assets pair is still new so it's under testing. Do let me know if you see anything out of place

ex:

http://xcp.blockscan.com/api2.aspx?module=price&asset1=BTC&asset2=SJCX

http://xcp.blockscan.com/api2.aspx?module=price&asset1=SJCX&asset2=XCP
http://xcp.blockscan.com/api2.aspx?module=price&asset1=XCP&asset2=SJCX


Cheers

Great.  Thanks.

I noticed you added email notifications too.   

[mtbitcoin]

Great.  Thanks.

I noticed you added email notifications too.   

I like what you did with CoinMachine.co. Straight forward and clean design. Tried the service and the notifications were prompt and precise

[CounterpartyRippler]

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.

[mtbitcoin]

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?

[PhantomPhreak]

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.

[mtbitcoin]

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 ?

[PhantomPhreak]

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.)

[mtbitcoin]

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

I have updated both the order_matches and orderinfo(matches) with the block number

[weex]

I've started looking at the order matches screen and have a request. Would it be possible to have that sorted by price or pair then price? Otherwise, seeing more results per page would help with the usability.

Also, I've not looked at counterpartyd but are zero-confirmation orders something you could show? (maybe dimmed to show they aren't active yet)