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.
f4dcdfce839db844cccac8af18cda6a3857a1113d93d5c80faac1d155d7f92d5
Both payments are on their chains and locked to the same secret hash 31d69a2efeacdec502e266ac608198a918a01cfa, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: f4dcdfce839db844cccac8af18cda6a3857a1113d93d5c80faac1d155d7f92d5
- MakerPaymentSpent: 46d3e47f4cb6686d0739c1104dc521f572166c023ae1d4c0aefe7fae3e318463
027be82284b54a59afe1c7a957a96e447cb4bd9c09be81ac3d2b59537d5f2878
Both payments are on their chains and locked to the same secret hash 31d69a2efeacdec502e266ac608198a918a01cfa, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 47f9c8c5984605019e8a889d3059b0d842e7ff0a52f7711eb82fa8278f132995
- TakerPaymentSent · TakerPaymentReceived: 027be82284b54a59afe1c7a957a96e447cb4bd9c09be81ac3d2b59537d5f2878
- TakerPaymentSpent: 8f12b079504b271d66c81e4b2ac38d9dee3bc4ace5989c422f315935f07b30d1
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.