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.
ca4e78e436d5e6e5c6cf01a9e39c8ea3f2ff482173ad0a3936106ab20ca91c0b
Both payments are on their chains and locked to the same secret hash a0f69399d77a5c4c8f646b807277b233797a82a2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ca4e78e436d5e6e5c6cf01a9e39c8ea3f2ff482173ad0a3936106ab20ca91c0b
- MakerPaymentSpent: 377cc2bd812d4f28dc489acbc4758050d607b79d9007b336e4eb94dce1f3b29f
975a2d2c2e8ae425f85aeb971a1b1d886d8d400f298b2282d8b62ee9b6800625
Both payments are on their chains and locked to the same secret hash a0f69399d77a5c4c8f646b807277b233797a82a2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: de27648eb3dffe100828d0f3083bbbfdca9fe07d50a89241c5023539512195d4
- TakerPaymentSent · TakerPaymentReceived: 975a2d2c2e8ae425f85aeb971a1b1d886d8d400f298b2282d8b62ee9b6800625
- TakerPaymentSpent: 85a3778ee3e3f3041046fb8521201b551e13ca3d72494e253a9f855a06fc8289
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.