This one took about 2.2× the usual for FIRO/QTUM. 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.
dc4546e4bab27f2ac3471dbce7a9364a108b0b81d54fd3e6503917c453bc8564
Both payments are on their chains and locked to the same secret hash 5e3d09e5c07b3f0654271e7b75b87715ea8351bb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: dc4546e4bab27f2ac3471dbce7a9364a108b0b81d54fd3e6503917c453bc8564
a4b8d19bfa0db0f8ac45d3003ab48ca27401f175c533874ddb3d778c4cbfd2c8
Both payments are on their chains and locked to the same secret hash 5e3d09e5c07b3f0654271e7b75b87715ea8351bb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: d4611cd4906300b049aed215cf552907250a0c860f248a8edcc94b4ea950222c
- TakerPaymentReceived: a4b8d19bfa0db0f8ac45d3003ab48ca27401f175c533874ddb3d778c4cbfd2c8
- TakerPaymentSpent: ac8bfa5bfdd87c832d36ba698107367183eb81bf2711428f05d8127b819b7b56
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.