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.
21bf9f2868d1b5bed47682f0d54367025b61a3c8fa87d9c0461bbd8075bf9548
Both payments are on their chains and locked to the same secret hash ff495452912510b76a0fc814a118b42da531ed60, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 21bf9f2868d1b5bed47682f0d54367025b61a3c8fa87d9c0461bbd8075bf9548
- MakerPaymentSpent: 199ff1d2d64c7e09c77238eb36d125a20b8c93c38be8890a90e6d625eb9155b3
1cadf839df86a666c8627def890231efdd34cbdbbf70818d378cab369d108503
Both payments are on their chains and locked to the same secret hash ff495452912510b76a0fc814a118b42da531ed60, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6bccc1fb9e3837b09e6f45caf4dd636e90a367675bbd2bd3f9bc45473eb0b7e1
- TakerPaymentSent · TakerPaymentReceived: 1cadf839df86a666c8627def890231efdd34cbdbbf70818d378cab369d108503
- TakerPaymentSpent: c0cf769f6865a319fe3a43ca4fb229cb5e3191bac1e2b44c399f7c65f8e8f12e
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.