An atomic swap is not instant by design. Each side has to publish a transaction and wait for the other chain to confirm it, so the time it takes is set mostly by the block spacing of the two chains involved rather than by anything either party does.
0597d0614fad23f7f1b400e7e63ee289d5954ef60fdd29ab6b286f29af849af1
Both payments are on their chains and locked to the same secret hash 0de6e4d24eba8d1f8ca456482a393d309b1616b7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0597d0614fad23f7f1b400e7e63ee289d5954ef60fdd29ab6b286f29af849af1
- MakerPaymentSpent: c2d4e67aa833d9b55a76a799b8586ba46d753e347fc06a9f6c2025a98aef1366
5d0aecc325af8a33fc71c4f0b1c8a9c6293349b8102f44a020fab275ade93b8b
Both payments are on their chains and locked to the same secret hash 0de6e4d24eba8d1f8ca456482a393d309b1616b7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fa1ac2b9c6b7bdddf09f17e681b534321c7785c0900d80aad880f9cb7d2c5b75
- TakerPaymentSent · TakerPaymentReceived: 5d0aecc325af8a33fc71c4f0b1c8a9c6293349b8102f44a020fab275ade93b8b
- TakerPaymentSpent: d416b2cc9c75d651e514aa7feb9bec853a9864269430a70fa065ab4b1903369a
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.