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.
9d6e6a601b7e364b997d2bc93c9a2c9e608243655c9c548e740e891ecd47242f
Both payments are on their chains and locked to the same secret hash 1eabfc1b94008719223c7edc81a72d7d68caf857, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9d6e6a601b7e364b997d2bc93c9a2c9e608243655c9c548e740e891ecd47242f
- MakerPaymentSpent: 2f8144543fd3729676d6e268b5308921bd72c11ea8efca39e996069056986c7c
84bfb6bd56dedbf4809f6394e379237c5705f5a235903ac3f6b819a6fcaa93fe
Both payments are on their chains and locked to the same secret hash 1eabfc1b94008719223c7edc81a72d7d68caf857, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8e8d70f7eab66764433a2d1234c2cb619b2935612c6fb6ec7cf3df53caa99fd7
- TakerPaymentSent · TakerPaymentReceived: 84bfb6bd56dedbf4809f6394e379237c5705f5a235903ac3f6b819a6fcaa93fe
- TakerPaymentSpent: 91d82e5426e3181bc24324f56f0b2a7c8649fc1f0864fe2083bd26cdd755fcf2
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.