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.
fe2985a631ad53159e4d2ceffb35cc3c6df421421081d91498f0e87b4823c8a7
Both payments are on their chains and locked to the same secret hash 3a9c72098c13e6bad45ebb7ebd3703bab56a7d0f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: fe2985a631ad53159e4d2ceffb35cc3c6df421421081d91498f0e87b4823c8a7
- MakerPaymentSpent: ca7c1c0b553ab9258bfe9745dc5fec65db97fbcecd7c88e2ade5a70e3b41ca6e
0adf77a1c040c8a2a0905c1841388a3f84ce93436bc85c727ab9a2e07a2dad03
Both payments are on their chains and locked to the same secret hash 3a9c72098c13e6bad45ebb7ebd3703bab56a7d0f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3d2b289b5e259ed6dbd0c52bdb77dc7dc8dc501c1f6e805105ac9a16a7e3b19a
- TakerPaymentSent · TakerPaymentReceived: 0adf77a1c040c8a2a0905c1841388a3f84ce93436bc85c727ab9a2e07a2dad03
- TakerPaymentSpent: 9ab5c05322f0ee73ac21374de57dd93cf0e6c16ce9926c2232e303dca45b931d
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.