This one took about 2.0× the usual for FIRO/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.
8dbd23d34800e12a0975582aae10320f7b361e4a129399d45658fc86aaab7a0f
Both payments are on their chains and locked to the same secret hash 1264167a319668d4bede40dffbdec086bca438f3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 8dbd23d34800e12a0975582aae10320f7b361e4a129399d45658fc86aaab7a0f
15226d42d1ca89e56a6fb90e112b5da0b94bd6559a66c6c20d7277ef0c88d89f
Both payments are on their chains and locked to the same secret hash 1264167a319668d4bede40dffbdec086bca438f3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: dbbc7a0910bd00d9f56293f5299f2d1a492e4e69613502f8ab171edd729cf226
- TakerPaymentReceived: 15226d42d1ca89e56a6fb90e112b5da0b94bd6559a66c6c20d7277ef0c88d89f
- TakerPaymentSpent: d2d7d83ba7f920e9b9a6070c307042524750c6da0fd31d262f81687e064d87d4
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.