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.
be398b0b5cbfe7e7cb39a636d590d1e6f32c238143a9639ac3b42b0773fa0fb8
Both payments are on their chains and locked to the same secret hash 5d77d25484ac9f54d7b7541742f4b7eb5f9b861c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: be398b0b5cbfe7e7cb39a636d590d1e6f32c238143a9639ac3b42b0773fa0fb8
- MakerPaymentSpent: a1f3f1a52c17a2aeaed3b446d53ff98d308c2a3c3beaf966095d0256915bbf71
aca47005c831652a7f3477cd2033730ef3f9c5e08f0eee58a06f4720e3388e34
Both payments are on their chains and locked to the same secret hash 5d77d25484ac9f54d7b7541742f4b7eb5f9b861c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 00a832257eea83d1b18cc529a9c188099b127ce6d98f2fa5eb233a7d5ae3a250
- TakerPaymentSent · TakerPaymentReceived: aca47005c831652a7f3477cd2033730ef3f9c5e08f0eee58a06f4720e3388e34
- TakerPaymentSpent: 8a24e147dfdf85722cdbf3037d93213c74f2a53073a7a56520f83ca76a27104f
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.