I think it must be included in the wallet, otherwise it will not be wide used.
Yes, could be a good thing to include it in a wallet, but we don't have any right now
Topic: [Web service] Block Confirmation Alarm - free and opensource - (Read 2111 times)
Yes, could be a good thing to include it in a wallet, but we don't have any right now
Tired of waiting for bitcoin/litecoin/dogecoin transaction confirmations hitting F5 all the time?
Right now, I'm doing exactly this for last one hour. After block 369862, there is no block for last 80 minutes. 
P.S.: Once you tackle porting it to NXT,
you can immediately support NXT, HZ, BURST, FIM, ...
Great service!
Just discovered it through this google search:
https://www.google.de/search?q=audio+signal+when+next+bitcoin+block+is+confirmed
Especially with the current BTC illnesses, very cool that it exists. Even for 6 chains, kudos!
I am waiting for the 6th confirmation now ... for 1 hour and 12 minutes (since the last block)
Oh, and have a look, I have build something (slightly) related chaincountdown.py.
Just discovered it through this google search:
https://www.google.de/search?q=audio+signal+when+next+bitcoin+block+is+confirmed
Especially with the current BTC illnesses, very cool that it exists. Even for 6 chains, kudos!
I am waiting for the 6th confirmation now ... for 1 hour and 12 minutes (since the last block)
Oh, and have a look, I have build something (slightly) related chaincountdown.py.
February 05, 2015, 06:09:44 PM
This service is still available; try it and give us feedback, we really appreciate your help!
November 06, 2014, 06:43:44 AM
Now you can use Block Confirmation Alarm as a service!
You can easily implement Block Confirmation Alarm in your website, using our API.
This is an example:
http://blockconf.openbitlab.com/?hash=transactionhashcode&coin=btc&nconf=6
where:
You can easily implement Block Confirmation Alarm in your website, using our API.
This is an example:
http://blockconf.openbitlab.com/?hash=transactionhashcode&coin=btc&nconf=6
where:
- hash is the hash of the transaction
- coin is the coin code (btc,ltc,doge)
- nconf is the number of confirmations required
I think it must be included in the wallet, otherwise it will not be wide used.
Yes, could be a good thing to include it in a wallet, but we don't have any right now
I think it must be included in the wallet, otherwise it will not be wide used.
Tired of waiting for bitcoin/litecoin/dogecoin transaction confirmations hitting F5 all the time? This page allows you to keep tracking of confirmations for your bitcoin/litecoin/dogecoin transaction; after setup and after the reaching of confirmation target, the page will produce a notification.
You can put the transaction hash (leaving it blank the counting starts from current block). You can also set up the alarm on each new block and enable /disable audio notifications.
You can try our service here: http://blockconf.openbitlab.com/
We add here some screenshots to show the features:
This service is opensource, you can check the source code here: https://github.com/openbitlab/blockconfirmationalarm
For more information or updates please check http://openbitlab.com/, the platform where we collect all our ideas, and the related blog http://blog.openbitlab.com/ or write to us at:
[email protected]
[email protected]
If you like this service, feel free to make a donation to: 13gbybVyaYy5yA7Z7si2zJfo2Aat6d7c8z
Jump to: