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.
0a7a1af9f57a7ad1eaa3e7768ba80c775cbff2d5658613105675f3ec4bcd5ace
Both payments are on their chains and locked to the same secret hash af35445a5ddd42585450671aa25f031f6fd09334, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0a7a1af9f57a7ad1eaa3e7768ba80c775cbff2d5658613105675f3ec4bcd5ace
- MakerPaymentSpent: 8ed9b83e8ed7657efadad78eddbe1d1b0c96b20abf6d3a90026f1024d1c76ab6
279fde362b6d72900cac41fcea121b31bbf8524e7274a16433ac8e2d241edbb4
Both payments are on their chains and locked to the same secret hash af35445a5ddd42585450671aa25f031f6fd09334, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 73f145a48b6cd7a06fc8488e36f1d31af0f1b9a12ea890c2aee71cf6996028cc
- TakerPaymentSent · TakerPaymentReceived: 279fde362b6d72900cac41fcea121b31bbf8524e7274a16433ac8e2d241edbb4
- TakerPaymentSpent: 1c67782d5db38d847d5b2ea6dd373e4db3f92afef74f3a84f63a57a1ebb01b2e
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.