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.
c01c8991713aa11fc3b5a04f691316d61dc934a72fd33313e574afe6eca3aa53
Both payments are on their chains and locked to the same secret hash 29d8fde3f85696d563df541b3171ac66b394ebb3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c01c8991713aa11fc3b5a04f691316d61dc934a72fd33313e574afe6eca3aa53
- MakerPaymentSpent: 17d5c58115fb13fc13324aaddb23c92b2703f0aec4aab4eab284edc737ae1a49
d9ed7f016f91589678ddc113b626826da006299f20c5edec07ab2e541cf8ab0b
Both payments are on their chains and locked to the same secret hash 29d8fde3f85696d563df541b3171ac66b394ebb3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 83655af3afa941596bf16a842a607e8e95dd092b9f099e5914a9175f23438a74
- TakerPaymentSent · TakerPaymentReceived: d9ed7f016f91589678ddc113b626826da006299f20c5edec07ab2e541cf8ab0b
- TakerPaymentSpent: 9ba08bea4fc94b0fd2c9b758dbaecacaca0306c6a4d21a1693c12448b8b52a07
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.