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.
67fae5c4c7254594bc4ba1ef2df572de56a9c9832a0d786be8adc0a04051b359
Both payments are on their chains and locked to the same secret hash ce5985d9fac8d3f18140f15aa236291f7c5d63bb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 67fae5c4c7254594bc4ba1ef2df572de56a9c9832a0d786be8adc0a04051b359
- MakerPaymentSpent: 705ef6d724d3a6ffb3cf519a2aa011a273b3228297efc82ff13c87d52071c2e7
6f4bd6ea16b02004b31a58ea78419fd6124fd01da42a9ece9b1d3292ff62a743
Both payments are on their chains and locked to the same secret hash ce5985d9fac8d3f18140f15aa236291f7c5d63bb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0481b3ea27b18c6e8136e267db20b5cf1062fb5d06e7c4dcca5439a9b2a4383c
- TakerPaymentSent · TakerPaymentReceived: 6f4bd6ea16b02004b31a58ea78419fd6124fd01da42a9ece9b1d3292ff62a743
- TakerPaymentSpent: f38a3b514f53abcc55537b043b317cd0c2d6136ddda353f549b44170c353589b
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.