This one took about 2.0× the usual for DGB/LTC. Waiting longer than usual is not in itself a failure: a swap waits on confirmations from both chains, and a slow block or a busy network stretches it.
75dd5bfe57af1559e0bbb7e3dd279d8c33a81894894e546e2884ba8ccb0f24de
Both payments are on their chains and locked to the same secret hash e99b1c0ae00add8144b9d319a76c82b24e7136ea, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 75dd5bfe57af1559e0bbb7e3dd279d8c33a81894894e546e2884ba8ccb0f24de
- MakerPaymentSpent: 741711fb157f3bff898abab63f62fd4e10442d0d6e4a8f0084730cbd6fe91c26
873bd3a533734a3934886689f348932bc3b376bbf0d2853f2e0641bdabf15b4e
Both payments are on their chains and locked to the same secret hash e99b1c0ae00add8144b9d319a76c82b24e7136ea, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 71e1c6efd10f775138d25d97a1c5b85bda320df0a3aae269f8477a05e2b648e1
- TakerPaymentSent · TakerPaymentReceived: 873bd3a533734a3934886689f348932bc3b376bbf0d2853f2e0641bdabf15b4e
- TakerPaymentSpent: daf17ee03d2765cd50ab04374a2866d05440ce47e7a8526e9ba04b9606d28bb1
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by kdf-statsdb-8762.