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.
fb9012db755f0febbdfd34d537ed3f74755135d741ac76b666498157406b85f9
Both payments are on their chains and locked to the same secret hash e1446e03ab78421f6c593a6b0abf8e5645b41163, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: fb9012db755f0febbdfd34d537ed3f74755135d741ac76b666498157406b85f9
- MakerPaymentSpent: 7e24e2499347321d442234e0822a889b3af5afa348d1fd73c7424026433eae3a
2704bcb209d65c5a7d1aff688f5e662570312224ce800de8eb1702a7f7358530
Both payments are on their chains and locked to the same secret hash e1446e03ab78421f6c593a6b0abf8e5645b41163, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0fcbdb58a627b3a6c19c3350e2b433e57a42f4c06a9bf9848f699ef124c8e722
- TakerPaymentSent · TakerPaymentReceived: 2704bcb209d65c5a7d1aff688f5e662570312224ce800de8eb1702a7f7358530
- TakerPaymentSpent: 8226cc5f1e50c19e6f60de11a0fe50044e754d811b65b9cfe6576dafdba852e5
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.