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.
616d5ff45cf10ffc075d13f2f84b77226f065595316c49a70ee45d2128eee2a7
Both payments are on their chains and locked to the same secret hash f3c67ca93ae162b4fc022a1fb6e0ba7fd372bd13, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 616d5ff45cf10ffc075d13f2f84b77226f065595316c49a70ee45d2128eee2a7
- MakerPaymentSpent: 7ecc62fa6234c8f857ebecc47a6e96da2841f7cafd62ca28dc819fa2419310d6
28e7c901ef5b371eac952d6c065fb8502dfb37b5a3987c52072bf8710606e6ea
Both payments are on their chains and locked to the same secret hash f3c67ca93ae162b4fc022a1fb6e0ba7fd372bd13, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8df706ab7ecad62fd9d029d6a7f957c912aa78482c6f7fa63aa97755c9ee7645
- TakerPaymentSent · TakerPaymentReceived: 28e7c901ef5b371eac952d6c065fb8502dfb37b5a3987c52072bf8710606e6ea
- TakerPaymentSpent: 9e832d77cbd625e503fee51a62acf82211d636006798e9ec4f3493d0a7a84484
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.