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.
acd6400054b0c44862582abefa9385ffbf10ba7d0e27cd8a677f225d845ed22a
Both payments are on their chains and locked to the same secret hash 7ec8a8deaba87701adcf62a49cdb5271b68b8e95, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: acd6400054b0c44862582abefa9385ffbf10ba7d0e27cd8a677f225d845ed22a
- MakerPaymentSpent: ed5a17d0343c2e26fa792d7c584b43401058e10d10672ec64538ba13813f3ece
57b8c7f7e2bcc9bcd0a767f2375bb99e36e508cb7399722e44e57467e1691e24
Both payments are on their chains and locked to the same secret hash 7ec8a8deaba87701adcf62a49cdb5271b68b8e95, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 331373f28820f8f356a7ba98765afbfb508beccfad86d68dfebdc9b95c679032
- TakerPaymentSent · TakerPaymentReceived: 57b8c7f7e2bcc9bcd0a767f2375bb99e36e508cb7399722e44e57467e1691e24
- TakerPaymentSpent: dd66859cd36be1c02f5e1e41f7fe169a90718cf4ce22d2867e9819f7ec39dcff
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.