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.
f0605aff49be0eb4ce156b49eb7e57ce326d4100ce0d1992a5cc831c495e8b73
Both payments are on their chains and locked to the same secret hash 542c858e945fd2980ab95b7d9c0a21c4f18eb052, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f0605aff49be0eb4ce156b49eb7e57ce326d4100ce0d1992a5cc831c495e8b73
- MakerPaymentSpent: baf7aaf3c8acac152ecf485e66e29ed16747d91314b222e582a03d639872ce66
edc91b03808506c127a57f9519da7bc82bab5ff4a32f64130381498745fdac99
Both payments are on their chains and locked to the same secret hash 542c858e945fd2980ab95b7d9c0a21c4f18eb052, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: d86edece2ca8a73fd363975ea1f2dc6ab024d4c7f72d431a8970462d458c5e0e
- TakerPaymentSent · TakerPaymentReceived: edc91b03808506c127a57f9519da7bc82bab5ff4a32f64130381498745fdac99
- TakerPaymentSpent: 3c2930fc2873eb8ae013327cd823ee2e8ac7dd924715dc44d467cb3bc9320a4c
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.