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.
b317fd2f37d414ff0623301b1c784abf08e014c68957e0e7090821d01dc6090f
Both payments are on their chains and locked to the same secret hash fa5718d83e61f5ba452420f10c6c4c0d7e591e26, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b317fd2f37d414ff0623301b1c784abf08e014c68957e0e7090821d01dc6090f
- MakerPaymentSpent: 4b38fa16744d5b80a3b7d56be4314f397e5c964de6fb8f1ad552f31da966c945
18ca661ee6bd5327de3980746dc84c780111acfe508c6c14a003abe2a8556926
Both payments are on their chains and locked to the same secret hash fa5718d83e61f5ba452420f10c6c4c0d7e591e26, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ecf1024160d9fe50db2bf1e22cc35934f46aa8c616399ac5e1426491521171f5
- TakerPaymentSent · TakerPaymentReceived: 18ca661ee6bd5327de3980746dc84c780111acfe508c6c14a003abe2a8556926
- TakerPaymentSpent: da44df0e988f684058edd53ed663dfb374a96260057317fbb046703a3ebc5bc7
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.