This one took about 2.5× the usual for VRSC/DGB. 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.
1f8e2fbe6f3e26a62edb1c7a271da1fbd1eb587b104764cab4fccee8b7dbc5e1
Both payments are on their chains and locked to the same secret hash 15680f3ba63b4aaa9b71bf21d203bb954d93ab9d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 1f8e2fbe6f3e26a62edb1c7a271da1fbd1eb587b104764cab4fccee8b7dbc5e1
c55be1719268c8ea305ea7809a35738271c9300a1e3b0aea33028c779a2585dc
Both payments are on their chains and locked to the same secret hash 15680f3ba63b4aaa9b71bf21d203bb954d93ab9d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 592f7ec62cda84ac3eb3c3779aaa647cd7c64dab553b013261f17569ab4065fe
- TakerPaymentReceived: c55be1719268c8ea305ea7809a35738271c9300a1e3b0aea33028c779a2585dc
- TakerPaymentSpent: 91a97f38c13365a2e6f208bebf5cb05ab18265fcce1c39944efe745f3a0ed314
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 defistats-gleec.