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.
b29b02fd18657eca205fe71dac2e27b354f576ee80a4424af474144015891788
Both payments are on their chains and locked to the same secret hash 90e556a2395d11a76595f815e87470c455057b0e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b29b02fd18657eca205fe71dac2e27b354f576ee80a4424af474144015891788
- MakerPaymentSpent: 67756a1edd77e9abebf4733ee93fbdf21fa69bb8008d01ae4198c4108b697506
7d767cc5a3e0e5ce8c6322c81a9b0dcd4273ac5c06434d74bcb61481069362fd
Both payments are on their chains and locked to the same secret hash 90e556a2395d11a76595f815e87470c455057b0e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5ec85f0761f7f90b8c967f2c5c5ac140653c7947f594b4ae03c738f68b6af70d
- TakerPaymentReceived · TakerPaymentSent: 7d767cc5a3e0e5ce8c6322c81a9b0dcd4273ac5c06434d74bcb61481069362fd
- TakerPaymentSpent: 126724a4f7ca0b42010dc487cac65dac570b5ab51aa388006365332b7ff56cfc
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.