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.
8c60abedacdc5fc58a71c0358f9a2f17e860826cf2155e9908ca29380c4c393b
Both payments are on their chains and locked to the same secret hash d3b9d100b94338fff7b433f52829673fb78bcc5a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8c60abedacdc5fc58a71c0358f9a2f17e860826cf2155e9908ca29380c4c393b
- MakerPaymentSpent: af97648441e5968b1f5c8cad671c8ffac3997ffe0773fc790f17b07fd5c85b88
bff4528596d2172ad35daaa1a63aa670869e52c819846cc8684bfe4b148b89bf
Both payments are on their chains and locked to the same secret hash d3b9d100b94338fff7b433f52829673fb78bcc5a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 35365c08883afa24d84cbe9505aff441135b27daae2df56b1f749adf579dc72a
- TakerPaymentSent · TakerPaymentReceived: bff4528596d2172ad35daaa1a63aa670869e52c819846cc8684bfe4b148b89bf
- TakerPaymentSpent: 87efe3e113767b2dbd3a255f5925998d04415c3f5f9aed076c980dc2cbe7aaa0
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.