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.
72c24f44fa2cc9201a4df97e0876b002a96f244a6b0ef10e1bb46639f4bda8f1
Both payments are on their chains and locked to the same secret hash 3f0cc9387550ce4f1c01ae1f4b41b16f45b7bae3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 72c24f44fa2cc9201a4df97e0876b002a96f244a6b0ef10e1bb46639f4bda8f1
- MakerPaymentSpent: 70c76a80ea5fc2e1a0289655b8bccce36dc7e410ab8994daf867b2f59e53e78b
93492be9e3e08a0196485e8c02bd681fe87f8b6ee5b93695a8098778fbaa48e0
Both payments are on their chains and locked to the same secret hash 3f0cc9387550ce4f1c01ae1f4b41b16f45b7bae3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: fdb8f9c66ed4c0094a93ec9e7f9f36c74558e7312e6a554748306964cc7bf200
- TakerPaymentSent · TakerPaymentReceived: 93492be9e3e08a0196485e8c02bd681fe87f8b6ee5b93695a8098778fbaa48e0
- TakerPaymentSpent: c008a078a6f8a9499463f51e52862762f1fee6056217de379ab908b04d48884d
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.