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.
b5bbc3b7f3ee6dc26c53af8f6e2a588caceaae0246e312ecbbadab4787e4e58d
Both payments are on their chains and locked to the same secret hash 79aaeba1d78488a9455c74f2cef09da95566ee34, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b5bbc3b7f3ee6dc26c53af8f6e2a588caceaae0246e312ecbbadab4787e4e58d
- MakerPaymentSpent: 2327d869992705a8251f076d3cb838a5274b092bb99a210d91bb1e18b479a659
7f32de5fc476686c4e1236661e5de6571069474523ea6a01abf7f67dcd87923d
Both payments are on their chains and locked to the same secret hash 79aaeba1d78488a9455c74f2cef09da95566ee34, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a52916a486463a4ab46db0535f692087e585cfaf0bfe2fb68a048dfeaaf9457c
- TakerPaymentSent · TakerPaymentReceived: 7f32de5fc476686c4e1236661e5de6571069474523ea6a01abf7f67dcd87923d
- TakerPaymentSpent: 3ca66451362f9016f748edf34859e7ed99e9118799d511510f53f603a55ba349
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.