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.
a0abfcb4b6a5945d50cd23393bbe1ad6ea0d92f1378692344cdfba2c9d950241
Both payments are on their chains and locked to the same secret hash b85bf5315af560c3b85bf91f622d71273ed1fbcb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a0abfcb4b6a5945d50cd23393bbe1ad6ea0d92f1378692344cdfba2c9d950241
- MakerPaymentSpent: 6bfc9b1fe7bd4978430d848971a95f108573dc6eddd0d6ba5277ecd8865ba1eb
839768e2db9218feed902c7abae80cda5f6d3ed231aca315a31bd126387dd878
Both payments are on their chains and locked to the same secret hash b85bf5315af560c3b85bf91f622d71273ed1fbcb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 56dbbaa1792cc20d2eb4c15b73abb54d21486e9d45f8360b4d62dd4f4d513587
- TakerPaymentSent · TakerPaymentReceived: 839768e2db9218feed902c7abae80cda5f6d3ed231aca315a31bd126387dd878
- TakerPaymentSpent: 740a566b8a5a00addb9bbe34e141bf939079475a2d9e9e7704f88d12b6fca2ec
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.