Why was the "under 64000" bet retired? It was one of the more profitable bets for the house.
And what happened to the progressive bets? Two of the three have disappeared from the site overnight, including the one with the 98% RTP.
Topic: SatoshiDICE.com - The World's Most Popular Bitcoin Game - page 248. (Read 495688 times)
It looks like those are all pending now.
Yes. Almost caught up now.
The following are still outstanding:
Quote
728e71fa953478cdedddc7e7eb7fe971c04f2c09baf01a01d37ca50ba184d843 2 187088 14:00:50 Jul-01-12
6e38d52d19270f7e474ad8bc0ffdc750bc601d19e05446c34cf2d960146d09e2 1 187102 15:52:06 Jul-01-12
aa95e33dcd43c3828c929dcae22f56ad3a4ec7ab813174a8112d97cff6b38011 1 187102 15:52:06 Jul-01-12
3eb016af4edbb4e53372fbd870bb28e0113ca3e865d320f0c790c4217384d7e3 1 187108 17:22:12 Jul-01-12
692755a16ac619706aebeef61d71297ef9c99277a706a585cdfcb27c7ee80382 1 187122 20:03:43 Jul-01-12
0032dad95af4f2f7a3838f51a35c852bbd6096b21f1fe73783562fe9d7823668 8 187124 20:20:27 Jul-01-12
0032dad95af4f2f7a3838f51a35c852bbd6096b21f1fe73783562fe9d7823668 4 187124 20:20:27 Jul-01-12
56bde8eb17b73859b622390a9b99df1acf1028bc059939ba2ecb5b7fc2f3236f 1 187124 20:20:27 Jul-01-12
82dc968eedb8706d8190b7a3849922134a57726d6c5eb3ecfd6e8864a6755272 17 187124 20:20:27 Jul-01-12
a16a360065317d2f7ef0c908f1ae89afbf83978efd01bcb9ab83d5849320a7a7 13 187124 20:20:27 Jul-01-12
76b24949282b27eff1e23f43a2cb013b091e8ccc50530a1fef345e303c376203 9 187131 21:33:50 Jul-01-12
0b157926112fa8e94935b4f17ffcaf9f3cf3b8355e283bce1da8ecaf52d41b3e 3 187135 22:11:05 Jul-01-12
0b157926112fa8e94935b4f17ffcaf9f3cf3b8355e283bce1da8ecaf52d41b3e 9 187135 22:11:05 Jul-01-12
7ba07cf788097760a83152cc7fbd9d2e8a8464613d9b03037527e3e8f3938728 9 187135 22:11:05 Jul-01-12
06b032a68ac001b2a22c4b75e9e980cc61f51e85a91036f8d42b91f5196b6c9c 6 187135 22:11:05 Jul-01-12
0b157926112fa8e94935b4f17ffcaf9f3cf3b8355e283bce1da8ecaf52d41b3e 4 187135 22:11:05 Jul-01-12
b2f1078df67bbd11161107f9ee6e419cac68c9a724c2a7b170cd172e33da0aed 1 187140 22:42:16 Jul-01-12
85302fbce2cb97d8bf1f888032cb5238dfb379094982bbeb26cb1420e0bb035d 1 187150 00:43:25 Jul-02-12
3fdadb9c8c052348183c2e229953cfcd1d072689c0122c7bf35b8f7370812d7d 0 187156 02:01:59 Jul-02-12
1c8b0bc4b58b2925a6c674b2a1c3a2e5dedd4b5c129f3c050d6771025f665aed 1 187174 03:59:22 Jul-02-12
19a08e829dd7547eae74cd9093810de267231125ee565728b6f4fee7d35aa201 0 187186 05:07:16 Jul-02-12
033a588bcdee73c23a646856436068cfef811e3a0a38b5f8c04fc878be82281a 1 187189 05:30:35 Jul-02-12
401b92e4f20ef50f8024e58ad0d9e78ace486be48e08e98a9d5540af6b3be28a 0 187189 05:30:35 Jul-02-12
b70bc1680b32280d5cf85f07f371aa13a90c21e21e90e3b4d279c8fa63974db7 1 187199 06:18:57 Jul-02-12
2e44b11c4fdf49fbf1808dac96fba90c10d13da094c7882c210f6c79b2d53794 1 187199 06:18:57 Jul-02-12
8353b7513d2f925f3b725304ba5a11b3cdf5972941fd3dc525dc64aac57298f0 1 187199 06:18:57 Jul-02-12
66051fe4fe6d720b70b4390ac49df2126abfd11bc9cf36283593b81d0b623bec 1 187220 08:53:50 Jul-02-12
6e38d52d19270f7e474ad8bc0ffdc750bc601d19e05446c34cf2d960146d09e2 1 187102 15:52:06 Jul-01-12
aa95e33dcd43c3828c929dcae22f56ad3a4ec7ab813174a8112d97cff6b38011 1 187102 15:52:06 Jul-01-12
3eb016af4edbb4e53372fbd870bb28e0113ca3e865d320f0c790c4217384d7e3 1 187108 17:22:12 Jul-01-12
692755a16ac619706aebeef61d71297ef9c99277a706a585cdfcb27c7ee80382 1 187122 20:03:43 Jul-01-12
0032dad95af4f2f7a3838f51a35c852bbd6096b21f1fe73783562fe9d7823668 8 187124 20:20:27 Jul-01-12
0032dad95af4f2f7a3838f51a35c852bbd6096b21f1fe73783562fe9d7823668 4 187124 20:20:27 Jul-01-12
56bde8eb17b73859b622390a9b99df1acf1028bc059939ba2ecb5b7fc2f3236f 1 187124 20:20:27 Jul-01-12
82dc968eedb8706d8190b7a3849922134a57726d6c5eb3ecfd6e8864a6755272 17 187124 20:20:27 Jul-01-12
a16a360065317d2f7ef0c908f1ae89afbf83978efd01bcb9ab83d5849320a7a7 13 187124 20:20:27 Jul-01-12
76b24949282b27eff1e23f43a2cb013b091e8ccc50530a1fef345e303c376203 9 187131 21:33:50 Jul-01-12
0b157926112fa8e94935b4f17ffcaf9f3cf3b8355e283bce1da8ecaf52d41b3e 3 187135 22:11:05 Jul-01-12
0b157926112fa8e94935b4f17ffcaf9f3cf3b8355e283bce1da8ecaf52d41b3e 9 187135 22:11:05 Jul-01-12
7ba07cf788097760a83152cc7fbd9d2e8a8464613d9b03037527e3e8f3938728 9 187135 22:11:05 Jul-01-12
06b032a68ac001b2a22c4b75e9e980cc61f51e85a91036f8d42b91f5196b6c9c 6 187135 22:11:05 Jul-01-12
0b157926112fa8e94935b4f17ffcaf9f3cf3b8355e283bce1da8ecaf52d41b3e 4 187135 22:11:05 Jul-01-12
b2f1078df67bbd11161107f9ee6e419cac68c9a724c2a7b170cd172e33da0aed 1 187140 22:42:16 Jul-01-12
85302fbce2cb97d8bf1f888032cb5238dfb379094982bbeb26cb1420e0bb035d 1 187150 00:43:25 Jul-02-12
3fdadb9c8c052348183c2e229953cfcd1d072689c0122c7bf35b8f7370812d7d 0 187156 02:01:59 Jul-02-12
1c8b0bc4b58b2925a6c674b2a1c3a2e5dedd4b5c129f3c050d6771025f665aed 1 187174 03:59:22 Jul-02-12
19a08e829dd7547eae74cd9093810de267231125ee565728b6f4fee7d35aa201 0 187186 05:07:16 Jul-02-12
033a588bcdee73c23a646856436068cfef811e3a0a38b5f8c04fc878be82281a 1 187189 05:30:35 Jul-02-12
401b92e4f20ef50f8024e58ad0d9e78ace486be48e08e98a9d5540af6b3be28a 0 187189 05:30:35 Jul-02-12
b70bc1680b32280d5cf85f07f371aa13a90c21e21e90e3b4d279c8fa63974db7 1 187199 06:18:57 Jul-02-12
2e44b11c4fdf49fbf1808dac96fba90c10d13da094c7882c210f6c79b2d53794 1 187199 06:18:57 Jul-02-12
8353b7513d2f925f3b725304ba5a11b3cdf5972941fd3dc525dc64aac57298f0 1 187199 06:18:57 Jul-02-12
66051fe4fe6d720b70b4390ac49df2126abfd11bc9cf36283593b81d0b623bec 1 187220 08:53:50 Jul-02-12
Are they on your radar too?
I checked the first 3 and they don't have unconfirmed payments - it looks like you didn't process them yet.
Yeah 
there are makes lot of -minus and i hope it will be chance with the new 25 BET on the lower tables
there are makes lot of -minus and i hope it will be chance with the new 25 BET on the lower tables 
Yeah, I think I worked out the issue here. Basically transactions were being saved into the wallet db and not the tracking/bet db so I didn't see that they were not being confirmed. I've corrected some ordering there so it should always be left in a state such that if anything is wrong it will be clear in my reports.
These are still pending and more than 2 days old:
Quote
2b7f6c3bf01743d298950143e7a65ba675a5328b734308555e41cf92dc43e00c 1 186466 03:55:03 Jun-27-12
45a8db8ff3c1975ddeb386098b2ed47e78595a30ec6a53797af244fb0d068783 1 186540 15:20:32 Jun-27-12
23ed6faf4a756d6ee544d670902139a14bb7eddb376bd2b88a679480fa6b1ee7 1 186564 19:53:19 Jun-27-12
12f33b47d5afb84de5c0fee7d096705712e89e7dbe5f07395cbfdadba0e8d48f 1 186575 21:35:17 Jun-27-12
16fd63d59ad469302204c5e19c75de2a3da32a3c79ec151b5b1019a9a9dfb863 4 186590 23:14:19 Jun-27-12
2fcdecd734dc3d0eb7387b195835a32e227291cccad48e9fba778a52977797be 1 186592 00:05:09 Jun-28-12
10cfa58ae5b934cf648e3898ecb5cbd80a636f1318c7f3cffcfbeef9fb30ce8e 4 186602 02:33:26 Jun-28-12
0d1d987a6d222ee5a546133d99ea001120c1e0489eab7170f712a0eda90094c4 1 186602 02:33:26 Jun-28-12
3c54f2c07dea29243b1a218b01f7667b04d327d45044facf77d16ccab08b8556 3 186611 04:17:25 Jun-28-12
02cbe2d2ee4bcdec3763057546d6e62f8bbc88ea6b410a74d19b4fc4e7da0978 2 186689 18:03:39 Jun-28-12
440a0b3b6554f03f2b9d3e160e418ec8c7903ae5f6d8844676cdef774c6e4093 0 186763 05:41:43 Jun-29-12
298df14aeab863473212cf017bb1c54ecd79ddbd0b5e37a68078310524c6b427 0 186852 20:55:59 Jun-29-12
45a8db8ff3c1975ddeb386098b2ed47e78595a30ec6a53797af244fb0d068783 1 186540 15:20:32 Jun-27-12
23ed6faf4a756d6ee544d670902139a14bb7eddb376bd2b88a679480fa6b1ee7 1 186564 19:53:19 Jun-27-12
12f33b47d5afb84de5c0fee7d096705712e89e7dbe5f07395cbfdadba0e8d48f 1 186575 21:35:17 Jun-27-12
16fd63d59ad469302204c5e19c75de2a3da32a3c79ec151b5b1019a9a9dfb863 4 186590 23:14:19 Jun-27-12
2fcdecd734dc3d0eb7387b195835a32e227291cccad48e9fba778a52977797be 1 186592 00:05:09 Jun-28-12
10cfa58ae5b934cf648e3898ecb5cbd80a636f1318c7f3cffcfbeef9fb30ce8e 4 186602 02:33:26 Jun-28-12
0d1d987a6d222ee5a546133d99ea001120c1e0489eab7170f712a0eda90094c4 1 186602 02:33:26 Jun-28-12
3c54f2c07dea29243b1a218b01f7667b04d327d45044facf77d16ccab08b8556 3 186611 04:17:25 Jun-28-12
02cbe2d2ee4bcdec3763057546d6e62f8bbc88ea6b410a74d19b4fc4e7da0978 2 186689 18:03:39 Jun-28-12
440a0b3b6554f03f2b9d3e160e418ec8c7903ae5f6d8844676cdef774c6e4093 0 186763 05:41:43 Jun-29-12
298df14aeab863473212cf017bb1c54ecd79ddbd0b5e37a68078310524c6b427 0 186852 20:55:59 Jun-29-12
It looks like those are all pending now.
Yeah, I think I worked out the issue here. Basically transactions were being saved into the wallet db and not the tracking/bet db so I didn't see that they were not being confirmed. I've corrected some ordering there so it should always be left in a state such that if anything is wrong it will be clear in my reports.
These are still pending and more than 2 days old:
Quote
2b7f6c3bf01743d298950143e7a65ba675a5328b734308555e41cf92dc43e00c 1 186466 03:55:03 Jun-27-12
45a8db8ff3c1975ddeb386098b2ed47e78595a30ec6a53797af244fb0d068783 1 186540 15:20:32 Jun-27-12
23ed6faf4a756d6ee544d670902139a14bb7eddb376bd2b88a679480fa6b1ee7 1 186564 19:53:19 Jun-27-12
12f33b47d5afb84de5c0fee7d096705712e89e7dbe5f07395cbfdadba0e8d48f 1 186575 21:35:17 Jun-27-12
16fd63d59ad469302204c5e19c75de2a3da32a3c79ec151b5b1019a9a9dfb863 4 186590 23:14:19 Jun-27-12
2fcdecd734dc3d0eb7387b195835a32e227291cccad48e9fba778a52977797be 1 186592 00:05:09 Jun-28-12
10cfa58ae5b934cf648e3898ecb5cbd80a636f1318c7f3cffcfbeef9fb30ce8e 4 186602 02:33:26 Jun-28-12
0d1d987a6d222ee5a546133d99ea001120c1e0489eab7170f712a0eda90094c4 1 186602 02:33:26 Jun-28-12
3c54f2c07dea29243b1a218b01f7667b04d327d45044facf77d16ccab08b8556 3 186611 04:17:25 Jun-28-12
02cbe2d2ee4bcdec3763057546d6e62f8bbc88ea6b410a74d19b4fc4e7da0978 2 186689 18:03:39 Jun-28-12
440a0b3b6554f03f2b9d3e160e418ec8c7903ae5f6d8844676cdef774c6e4093 0 186763 05:41:43 Jun-29-12
298df14aeab863473212cf017bb1c54ecd79ddbd0b5e37a68078310524c6b427 0 186852 20:55:59 Jun-29-12
45a8db8ff3c1975ddeb386098b2ed47e78595a30ec6a53797af244fb0d068783 1 186540 15:20:32 Jun-27-12
23ed6faf4a756d6ee544d670902139a14bb7eddb376bd2b88a679480fa6b1ee7 1 186564 19:53:19 Jun-27-12
12f33b47d5afb84de5c0fee7d096705712e89e7dbe5f07395cbfdadba0e8d48f 1 186575 21:35:17 Jun-27-12
16fd63d59ad469302204c5e19c75de2a3da32a3c79ec151b5b1019a9a9dfb863 4 186590 23:14:19 Jun-27-12
2fcdecd734dc3d0eb7387b195835a32e227291cccad48e9fba778a52977797be 1 186592 00:05:09 Jun-28-12
10cfa58ae5b934cf648e3898ecb5cbd80a636f1318c7f3cffcfbeef9fb30ce8e 4 186602 02:33:26 Jun-28-12
0d1d987a6d222ee5a546133d99ea001120c1e0489eab7170f712a0eda90094c4 1 186602 02:33:26 Jun-28-12
3c54f2c07dea29243b1a218b01f7667b04d327d45044facf77d16ccab08b8556 3 186611 04:17:25 Jun-28-12
02cbe2d2ee4bcdec3763057546d6e62f8bbc88ea6b410a74d19b4fc4e7da0978 2 186689 18:03:39 Jun-28-12
440a0b3b6554f03f2b9d3e160e418ec8c7903ae5f6d8844676cdef774c6e4093 0 186763 05:41:43 Jun-29-12
298df14aeab863473212cf017bb1c54ecd79ddbd0b5e37a68078310524c6b427 0 186852 20:55:59 Jun-29-12
No, it just chokes apparently at random on a very small percentage of transactions. I don't know what causes it - I occasionally post a list of outstanding transactions, and fireduck sometimes fixes them. I posted a list yesterday, but they're still not fixed.
Yeah, I think I worked out the issue here. Basically transactions were being saved into the wallet db and not the tracking/bet db so I didn't see that they were not being confirmed. I've corrected some ordering there so it should always be left in a state such that if anything is wrong it will be clear in my reports.
After a few hundred thousand transactions anything that can go wrong will.
Is satoshi dice currently choking on sendmany transactions?
I have a tx where a bet doesn't seem to have gotten into your db:
9ebfdbeb116616e748bc8654131b90ab21a7125ba376935a0984939159cd6f0f
I have a tx where a bet doesn't seem to have gotten into your db:
9ebfdbeb116616e748bc8654131b90ab21a7125ba376935a0984939159cd6f0f
No, it just chokes apparently at random on a very small percentage of transactions. I don't know what causes it - I occasionally post a list of outstanding transactions, and fireduck sometimes fixes them. I posted a list yesterday, but they're still not fixed.
Is satoshi dice currently choking on sendmany transactions?
I have a tx where a bet doesn't seem to have gotten into your db:
9ebfdbeb116616e748bc8654131b90ab21a7125ba376935a0984939159cd6f0f
I have a tx where a bet doesn't seem to have gotten into your db:
9ebfdbeb116616e748bc8654131b90ab21a7125ba376935a0984939159cd6f0f
Wouldn't this still be traceable back to you?
Yes. Everyone can see "address A bet X BTC and asked for their winnings to be sent to address B".
Not ideal for money laundering!
satoshidice due to the 0 confirmations makes for an awesome bitcoin laundering system 
But charges 27%... there must be cheaper ways to clean 100 BTC. Bet 5 BTC on "lessthan 48000" 20 times and you'll probably do better than losing 27%.
There is a way to send the winnings to a 3rd address, not to the same one.
http://www.satoshidice.com/advanced.php
Wouldn't this still be traceable back to you?
satoshidice due to the 0 confirmations makes for an awesome bitcoin laundering system
But charges 27%... there must be cheaper ways to clean 100 BTC. Bet 5 BTC on "lessthan 48000" 20 times and you'll probably do better than losing 27%.
There is a way to send the winnings to a 3rd address, not to the same one.
http://www.satoshidice.com/advanced.php
That scrennshot tells me nothing.
Tx id's do tell the story, screenshots are nothing more than noise. Especially when you name your address "wall3t" instead of showing it.
The blockchain doesn't lie. Incredible, isn't it?
Also, do you even realise that there is no transaction with that value on the address that you say the 2cents are missing, so, it can't be the same address?
How about you go to your Bitcoin client options and mark the checkbox that says "Show addresses in tx list"?
Then you'll see that the address you so conveniently call "wall3t" is this one: 1Jc9rBK9UcBDFczSiR6sCn3KAZaKeNCvuY
Also: STOP LABELING ALL YOUR ADDRESSES WITH "wall3t"!
FFS...
Tx id's do tell the story, screenshots are nothing more than noise. Especially when you name your address "wall3t" instead of showing it.
The blockchain doesn't lie. Incredible, isn't it?
Also, do you even realise that there is no transaction with that value on the address that you say the 2cents are missing, so, it can't be the same address?
How about you go to your Bitcoin client options and mark the checkbox that says "Show addresses in tx list"?
Then you'll see that the address you so conveniently call "wall3t" is this one: 1Jc9rBK9UcBDFczSiR6sCn3KAZaKeNCvuY
Also: STOP LABELING ALL YOUR ADDRESSES WITH "wall3t"!
FFS...
I really don't care either way, this was just a little toying with gambling and free spare change, I'm just curious what happened to that .02 that seems to have vanished and what implications that would have on larger gambles. As shown by my wallet, it obviously wasn't in that payment.
The 0.05240186 payment is your winnings from this bet. You bet 0.04 on "lessthan 48000" and won:
http://www.satoshidice.com/lookup.php?tx=5df14eb7a279fb557dea1afae70cdcca23bfe6821c55ae9553dbc18904f2640a
Your winnings of 0.0787528 appeared in the same block. Look at the 'transactions' tab. Do you see it there? The 'overview' tab that you showed us only shows the 3 most recent transactions.
Quote
Details Processed Bet Bet Tx Pay Tx Address Pay Status Bet Amount Result Payment Amount Lucky
Details 2012-07-01 03:36:12 lessthan 32000 b062134b 5bdd18a1 1LtYUNi 0.04000000 WIN 0.07875280 8738
Details 2012-07-01 03:36:12 lessthan 32000 b062134b 5bdd18a1 1LtYUNi 0.04000000 WIN 0.07875280 8738
Uncomfirmed (Actually received): 0.05240187 BTC
A little short, eh?
http://blockexplorer.com/tx/5bdd18a15db46269301c02782dd2ec0e7dee126ef2d93ea0fec28da0734ce940#o0 shows you received the full amount. It's in the same block as your bet.
So, what you're saying is that the blockchain that every Bitcoin node has in them is wrong and you are right, right?
I find that difficult to believe...
Also, blockchain.info agress with blockexplorer.com and it clearly shows the payment of 0.0787528 BTC going to your address 1LtYUNi4sjNEtJtRdqgstbngKxhtAtX95R and that you already spent it on a 0.23 BTC bet at satoshidice http://blockchain.info/tx-index/10996110/2fbb0b2845e57217a8afb242026715eaadce810b6e165e198df41ff39f945f0b 45 min after you received it lol
...?
I really don't care either way, this was just a little toying with gambling and free spare change, I'm just curious what happened to that .02 that seems to have vanished and what implications that would have on larger gambles. As shown by my wallet, it obviously wasn't in that payment.
Quote
Details Processed Bet Bet Tx Pay Tx Address Pay Status Bet Amount Result Payment Amount Lucky
Details 2012-07-01 03:36:12 lessthan 32000 b062134b 5bdd18a1 1LtYUNi 0.04000000 WIN 0.07875280 8738
Details 2012-07-01 03:36:12 lessthan 32000 b062134b 5bdd18a1 1LtYUNi 0.04000000 WIN 0.07875280 8738
Uncomfirmed (Actually received): 0.05240187 BTC
A little short, eh?
http://blockexplorer.com/tx/5bdd18a15db46269301c02782dd2ec0e7dee126ef2d93ea0fec28da0734ce940#o0 shows you received the full amount. It's in the same block as your bet.
So, what you're saying is that the blockchain that every Bitcoin node has in them is wrong and you are right, right?
I find that difficult to believe...
Also, blockchain.info agress with blockexplorer.com and it clearly shows the payment of 0.0787528 BTC going to your address 1LtYUNi4sjNEtJtRdqgstbngKxhtAtX95R and that you already spent it on a 0.23 BTC bet at satoshidice http://blockchain.info/tx-index/10996110/2fbb0b2845e57217a8afb242026715eaadce810b6e165e198df41ff39f945f0b 45 min after you received it lol
Quote
Details Processed Bet Bet Tx Pay Tx Address Pay Status Bet Amount Result Payment Amount Lucky
Details 2012-07-01 03:36:12 lessthan 32000 b062134b 5bdd18a1 1LtYUNi 0.04000000 WIN 0.07875280 8738
Details 2012-07-01 03:36:12 lessthan 32000 b062134b 5bdd18a1 1LtYUNi 0.04000000 WIN 0.07875280 8738
Uncomfirmed (Actually received): 0.05240187 BTC
A little short, eh?
http://blockexplorer.com/tx/5bdd18a15db46269301c02782dd2ec0e7dee126ef2d93ea0fec28da0734ce940#o0 shows you received the full amount. It's in the same block as your bet.
That got missed, maybe it wasn't old enough when I ran my program. I was basically deleting transactions that haven't confirmed in over two days.
It is handled now.
It is handled now.
It looks like you're still missing bets:
Quote
transaction id out block timestamp
---------------------------------------------------------------- --- ------ ------------------
2b7f6c3bf01743d298950143e7a65ba675a5328b734308555e41cf92dc43e00c 1 186466 03:55:03 Jun-27-12
45a8db8ff3c1975ddeb386098b2ed47e78595a30ec6a53797af244fb0d068783 1 186540 15:20:32 Jun-27-12
23ed6faf4a756d6ee544d670902139a14bb7eddb376bd2b88a679480fa6b1ee7 1 186564 19:53:19 Jun-27-12
12f33b47d5afb84de5c0fee7d096705712e89e7dbe5f07395cbfdadba0e8d48f 1 186575 21:35:17 Jun-27-12
16fd63d59ad469302204c5e19c75de2a3da32a3c79ec151b5b1019a9a9dfb863 4 186590 23:14:19 Jun-27-12
2fcdecd734dc3d0eb7387b195835a32e227291cccad48e9fba778a52977797be 1 186592 00:05:09 Jun-28-12
10cfa58ae5b934cf648e3898ecb5cbd80a636f1318c7f3cffcfbeef9fb30ce8e 4 186602 02:33:26 Jun-28-12
0d1d987a6d222ee5a546133d99ea001120c1e0489eab7170f712a0eda90094c4 1 186602 02:33:26 Jun-28-12
3c54f2c07dea29243b1a218b01f7667b04d327d45044facf77d16ccab08b8556 3 186611 04:17:25 Jun-28-12
02cbe2d2ee4bcdec3763057546d6e62f8bbc88ea6b410a74d19b4fc4e7da0978 2 186689 18:03:39 Jun-28-12
---------------------------------------------------------------- --- ------ ------------------
2b7f6c3bf01743d298950143e7a65ba675a5328b734308555e41cf92dc43e00c 1 186466 03:55:03 Jun-27-12
45a8db8ff3c1975ddeb386098b2ed47e78595a30ec6a53797af244fb0d068783 1 186540 15:20:32 Jun-27-12
23ed6faf4a756d6ee544d670902139a14bb7eddb376bd2b88a679480fa6b1ee7 1 186564 19:53:19 Jun-27-12
12f33b47d5afb84de5c0fee7d096705712e89e7dbe5f07395cbfdadba0e8d48f 1 186575 21:35:17 Jun-27-12
16fd63d59ad469302204c5e19c75de2a3da32a3c79ec151b5b1019a9a9dfb863 4 186590 23:14:19 Jun-27-12
2fcdecd734dc3d0eb7387b195835a32e227291cccad48e9fba778a52977797be 1 186592 00:05:09 Jun-28-12
10cfa58ae5b934cf648e3898ecb5cbd80a636f1318c7f3cffcfbeef9fb30ce8e 4 186602 02:33:26 Jun-28-12
0d1d987a6d222ee5a546133d99ea001120c1e0489eab7170f712a0eda90094c4 1 186602 02:33:26 Jun-28-12
3c54f2c07dea29243b1a218b01f7667b04d327d45044facf77d16ccab08b8556 3 186611 04:17:25 Jun-28-12
02cbe2d2ee4bcdec3763057546d6e62f8bbc88ea6b410a74d19b4fc4e7da0978 2 186689 18:03:39 Jun-28-12
It doesn't seem to be just that the payment isn't confirmed, because the bets aren't in your database at all as far as I can see.
Quote
Details Processed Bet Bet Tx Pay Tx Address Pay Status Bet Amount Result Payment Amount Lucky
Details 2012-07-01 03:36:12 lessthan 32000 b062134b 5bdd18a1 1LtYUNi 0.04000000 WIN 0.07875280 8738
Details 2012-07-01 03:36:12 lessthan 32000 b062134b 5bdd18a1 1LtYUNi 0.04000000 WIN 0.07875280 8738
Uncomfirmed (Actually received): 0.05240187 BTC
A little short, eh?
http://blockexplorer.com/tx/5bdd18a15db46269301c02782dd2ec0e7dee126ef2d93ea0fec28da0734ce940#o0 shows you received the full amount. It's in the same block as your bet.
Quote
Details Processed Bet Bet Tx Pay Tx Address Pay Status Bet Amount Result Payment Amount Lucky
Details 2012-07-01 03:36:12 lessthan 32000 b062134b 5bdd18a1 1LtYUNi 0.04000000 WIN 0.07875280 8738
Details 2012-07-01 03:36:12 lessthan 32000 b062134b 5bdd18a1 1LtYUNi 0.04000000 WIN 0.07875280 8738
Uncomfirmed (Actually received): 0.05240187 BTC
A little short, eh?
Jump to: