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.
250ac70c0562859ac81414ebc6035e678f6cc0600feecc081bddfdd389564cfc
Both payments are on their chains and locked to the same secret hash 5df44aaba49ef9e0abee60e0456278a439c69cae, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 250ac70c0562859ac81414ebc6035e678f6cc0600feecc081bddfdd389564cfc
- MakerPaymentSpent: a6582e7c88f77a3f922f408146b856ca61fb8885fafa63d14ac86f6bc100b83a
d93fd2dd4a222c231731796b2f63995fd4ca9b96660caf7d00c27266b633b743
Both payments are on their chains and locked to the same secret hash 5df44aaba49ef9e0abee60e0456278a439c69cae, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 1368049a2f3f8ff4bb1bde3400f5606b1cf0dd77ebe32047213bef2364e7bf50
- TakerPaymentSent · TakerPaymentReceived: d93fd2dd4a222c231731796b2f63995fd4ca9b96660caf7d00c27266b633b743
- TakerPaymentSpent: c9237bc75dd614ad34d74193578271e9db9f954f250215a489f8b54cb01ab673
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.