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.
049df7e49dcc96cb019fef06e749dc9ac6fed2fd4175b461fbb71ec0383086c3
Both payments are on their chains and locked to the same secret hash 216e5374d9930a513c1370a948b8d9817876ff62, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 049df7e49dcc96cb019fef06e749dc9ac6fed2fd4175b461fbb71ec0383086c3
- MakerPaymentSpent: 985ee4d5912a167e24e05259245fd1dc2c0d7158949b7830084cd5070c12720d
2ee0f3f7f05c8bba5e77a0af5a3f6a7ec748c0d81d13bd66643d8b453288351e
Both payments are on their chains and locked to the same secret hash 216e5374d9930a513c1370a948b8d9817876ff62, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 242a6be7396b3951cf368bf91b35351e2357468467a5eaa26a0122a44cd8ea6b
- TakerPaymentReceived · TakerPaymentSent: 2ee0f3f7f05c8bba5e77a0af5a3f6a7ec748c0d81d13bd66643d8b453288351e
- TakerPaymentSpent: c8ddb02e6fd6f18d28253f5f4bc4d7827a0ce9f7fb9f363142c4e1b8235a110f
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.