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.
b26e7f96727068774d7015b27bd6bf97ecf1163a685ecc67f7a32d15b3d7e1c8
Both payments are on their chains and locked to the same secret hash 65599c5c9348224674d216f3f9b6e5cf4b293ca7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b26e7f96727068774d7015b27bd6bf97ecf1163a685ecc67f7a32d15b3d7e1c8
- MakerPaymentSpent: 2f35335720099384056f74c30b269b75bb052a4c3e74ccd852fda77eda41db45
babbd14adeb079cd25f8e790929a5d4dfe2cb8f2a8e2cda7d4fc9aa0552c115f
Both payments are on their chains and locked to the same secret hash 65599c5c9348224674d216f3f9b6e5cf4b293ca7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 67aee8812152db823ac605984c67876129584ed5c2bc810fb50521dbb3fb33ee
- TakerPaymentSent · TakerPaymentReceived: babbd14adeb079cd25f8e790929a5d4dfe2cb8f2a8e2cda7d4fc9aa0552c115f
- TakerPaymentSpent: c8d3914b934871cb490befea3029145c03f34ff0d67af199a8d3ac9cecb8457e
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.