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.
436f4bbd3505f88ac39291b14e70671f308d2399f14a9e489f8fd50471997515
Both payments are on their chains and locked to the same secret hash abb1c4946d149dfd438e96fa5e6d793d019c002a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 436f4bbd3505f88ac39291b14e70671f308d2399f14a9e489f8fd50471997515
- MakerPaymentSpent: e66682336a4ab0e51aa7d18f6154d77bfd7b31cf56b4ca7d4c1209761b27edb0
83166a8b315d810f239b1b99dd38a274261748e6110eaa545615636153d204fa
Both payments are on their chains and locked to the same secret hash abb1c4946d149dfd438e96fa5e6d793d019c002a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7f765bba770c6ad24e3f5be036d96078fcb3822b6e7818c85c0e1e240c4520f1
- TakerPaymentSent · TakerPaymentReceived: 83166a8b315d810f239b1b99dd38a274261748e6110eaa545615636153d204fa
- TakerPaymentSpent: 8992258b25bc6dd5f56791f7013603a49ec4e1e58dc9a10cb5f7e3bd9a0551fe
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.