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.
2e68a953e1f0fd0f14e1abafe81b2dc7174745ff98594190cb25291cf5b1033c
Both payments are on their chains and locked to the same secret hash 3030091d0fd05ad74e81a02ca41fb11677c851e6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2e68a953e1f0fd0f14e1abafe81b2dc7174745ff98594190cb25291cf5b1033c
- MakerPaymentSpent: 77c96478efc8694b3f1d916c693d207b3322208b1f1a9a5a0498c91ebdd72b91
d270b20cbe3e7843c0f7a29b99f03dccba0e1560e159413dbab1ef2e59cf727d
Both payments are on their chains and locked to the same secret hash 3030091d0fd05ad74e81a02ca41fb11677c851e6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: a9932a2ad5adb4d318d61292f342a1e4aea109594267c712e3cfe74fe7f1d7ac
- TakerPaymentSent · TakerPaymentReceived: d270b20cbe3e7843c0f7a29b99f03dccba0e1560e159413dbab1ef2e59cf727d
- TakerPaymentSpent: f835836f5d345a1b94d42e9947652e3ec62cf6efbfe1cca5a8ce281a150d3919
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.