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.
7d8fd6673a6807b51c43dd95ff754203177c1d9213e442fdc886bd3d5501f7aa
Both payments are on their chains and locked to the same secret hash 55cdd5f25c1c868dc46383f2b323878197e8a816, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 7d8fd6673a6807b51c43dd95ff754203177c1d9213e442fdc886bd3d5501f7aa
- MakerPaymentSpent: 000a842440bad8f1cf6cb7382347fabd048a9c21f346c30cc302a0afac123589
b9eec8a9893a1d1020d3929a73be9f53c88349e082ca28303045010b5eef6ff5
Both payments are on their chains and locked to the same secret hash 55cdd5f25c1c868dc46383f2b323878197e8a816, and a preimage hashing to it was published on chain when one side claimed.
- TakerPaymentSent · TakerPaymentReceived: b9eec8a9893a1d1020d3929a73be9f53c88349e082ca28303045010b5eef6ff5
- TakerPaymentSpent: 3c99cd53bbf0321cc63c2d3bb1425fc039635b3814d50f9781f6a515b948eea4
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.