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.
d498941a95945750eb83cec33e838e256646f52869407f1555307d3c84c0d5d2
Both payments are on their chains and locked to the same secret hash 1384224303260d21c1a429d8199fe9bf08fd35e8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d498941a95945750eb83cec33e838e256646f52869407f1555307d3c84c0d5d2
- MakerPaymentSpent: a38de2fe7d0f68816e81bbf752a57557aa9498f0476ba107eb281372f8d290a9
b67a5a89a3d59762cf2d0fca19478235514991ea67635486e29dde594d702327
Both payments are on their chains and locked to the same secret hash 1384224303260d21c1a429d8199fe9bf08fd35e8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 564bbff26693b9c2677595ef0820a496f69490a4980c5b388b93425e518dced8
- TakerPaymentSent · TakerPaymentReceived: b67a5a89a3d59762cf2d0fca19478235514991ea67635486e29dde594d702327
- TakerPaymentSpent: 8d199f26065633120ccc2f246cdc07b922b126f4b1c5ad81714a6d63f8c7aaee
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.