--- Log opened Sun May 10 00:00:16 2020
01:56 -!- mol_ [~mol@unaffiliated/molly] has joined #bitcoin-builds
01:59 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 246 seconds]
02:05 -!- molz_ [~mol@unaffiliated/molly] has joined #bitcoin-builds
02:08 -!- mol_ [~mol@unaffiliated/molly] has quit [Ping timeout: 256 seconds]
02:33 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-builds
02:34 -!- mol_ [~mol@unaffiliated/molly] has joined #bitcoin-builds
02:36 -!- molz_ [~mol@unaffiliated/molly] has quit [Ping timeout: 256 seconds]
02:37 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 240 seconds]
03:31 -!- molz_ [~mol@unaffiliated/molly] has joined #bitcoin-builds
03:34 -!- mol_ [~mol@unaffiliated/molly] has quit [Ping timeout: 256 seconds]
04:22 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-builds
04:26 -!- molz_ [~mol@unaffiliated/molly] has quit [Ping timeout: 256 seconds]
04:31 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has quit [Read error: Connection reset by peer]
04:40 -!- gribble [~gribble@unaffiliated/nanotube/bot/gribble] has joined #bitcoin-builds
04:42 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 264 seconds]
05:21 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-builds
07:28 -!- mol [~mol@unaffiliated/molly] has quit [Read error: Connection reset by peer]
07:28 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-builds
07:41 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 272 seconds]
07:41 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-builds
08:12 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 264 seconds]
08:15 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-builds
09:04 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 260 seconds]
09:06 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-builds
13:58 -!- nnnn [b0e45250@176.228.82.80] has joined #bitcoin-builds
14:00 < nnnn> Hi, what can be the reason that with getrawtransaction vin points to 2 tx that end up with the same address? https://btc.com/eb6f9ce277aa2e3e58b9ddbc263292958697681a68f52bcb77fd358ea2132244  address bc1q8vsesycn8dw0ry48xugyw6jv9hc085xm86ahq0  is shown twice
14:46 -!- nnnn [b0e45250@176.228.82.80] has quit [Remote host closed the connection]
19:41 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 258 seconds]
19:43 -!- mol [~mol@unaffiliated/molly] has joined #bitcoin-builds
20:27 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Remote host closed the connection]
21:03 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-builds
21:25 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Remote host closed the connection]
21:26 -!- achow101 [~achow101@unaffiliated/achow101] has joined #bitcoin-builds
21:35 -!- mol_ [~mol@unaffiliated/molly] has joined #bitcoin-builds
21:39 -!- mol [~mol@unaffiliated/molly] has quit [Ping timeout: 256 seconds]
22:00 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has quit [Remote host closed the connection]
22:06 -!- sipa [~pw@gateway/tor-sasl/sipa1024] has joined #bitcoin-builds
22:39 -!- molz_ [~mol@unaffiliated/molly] has joined #bitcoin-builds
22:42 -!- mol_ [~mol@unaffiliated/molly] has quit [Ping timeout: 256 seconds]
23:02 -!- mol_ [~mol@unaffiliated/molly] has joined #bitcoin-builds
23:05 -!- molz_ [~mol@unaffiliated/molly] has quit [Ping timeout: 256 seconds]
23:20 -!- molz_ [~mol@unaffiliated/molly] has joined #bitcoin-builds
23:23 -!- mol_ [~mol@unaffiliated/molly] has quit [Ping timeout: 258 seconds]
--- Log closed Mon May 11 00:00:17 2020