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.
561c0f065e3328955499df6bac037b6694b838b3745d487d46c6f8206646f3c0
Both payments are on their chains and locked to the same secret hash 96b6d812236843eb38e607f0d6afefcdc8e0545f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 561c0f065e3328955499df6bac037b6694b838b3745d487d46c6f8206646f3c0
- MakerPaymentSpent: b335b7d287d2631e178d54131dfe1fc50245341b59c6374db02e9c7ad15d2506
79868a3b960243a106ae0b60276b47243c93e2191624331f41f160958c40f225
Both payments are on their chains and locked to the same secret hash 96b6d812236843eb38e607f0d6afefcdc8e0545f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: bb1f936967967ad22ade275b3c882ffc1897f81a3471202d0cfbc1fb785640a5
- TakerPaymentSent · TakerPaymentReceived: 79868a3b960243a106ae0b60276b47243c93e2191624331f41f160958c40f225
- TakerPaymentSpent: bab795f43b792acc5db0d888aad4a24b49a52d5ed12af45913a6d6b05a24e1dd
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.