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.
b8d86ff4fd2296109c4b581afca7abdf536069b5d2fab155de5a770dd80dc75c
Both payments are on their chains and locked to the same secret hash f47cf6d776153b2cc9ad808431b371a934094122, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b8d86ff4fd2296109c4b581afca7abdf536069b5d2fab155de5a770dd80dc75c
- MakerPaymentSpent: 71e099f8442b989e7452cf46d39543c3985b1ce8fa135afa8dc5bda9ed11cbbc
4c8d61f290c8b27dc58d16203403e3e8cdc3368fc36b49d767d753938265901a
Both payments are on their chains and locked to the same secret hash f47cf6d776153b2cc9ad808431b371a934094122, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0aadb0033d58c8e2368ecce2a3bde8743c75f0bece5cf9fa0ebd17ffe454cb9a
- TakerPaymentSent · TakerPaymentReceived: 4c8d61f290c8b27dc58d16203403e3e8cdc3368fc36b49d767d753938265901a
- TakerPaymentSpent: 052dde2c5c16d1be2bc0f46133009e75099597eb6fb70d7b6fc544431d9a2fb9
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.