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.
fdfde71e716e5aedf112838243c4a13da342eab446467eb9f625038147356974
Both payments are on their chains and locked to the same secret hash ff33b11bf467b4b69223a4aa2856aa6c60271671, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: fdfde71e716e5aedf112838243c4a13da342eab446467eb9f625038147356974
- MakerPaymentSpent: 7200b9770b572761141a1e4a0f568f7884c64042a132fde614963c6d846a68b6
5a1d794a0299db2f9fc1994345f8d1ecc072b57f9b49d8dbb720811566676875
Both payments are on their chains and locked to the same secret hash ff33b11bf467b4b69223a4aa2856aa6c60271671, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 460e069f9257f14a8106bed8a49c6db3a40ae091daf8ccf69ec3ad686e586b86
- TakerPaymentSent · TakerPaymentReceived: 5a1d794a0299db2f9fc1994345f8d1ecc072b57f9b49d8dbb720811566676875
- TakerPaymentSpent: 4a65c82821cf9253f32f2efe7db52abe6ac3d33e1e95b43a17bfef1c2b71e6a6
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.