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.
b578c1c7d174bb2395d58e37f795d5396ee1954f645faa28d002b00bbdd1f245
Both payments are on their chains and locked to the same secret hash 1730507198edea0cd39ed594f5ff65b37802961b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: b578c1c7d174bb2395d58e37f795d5396ee1954f645faa28d002b00bbdd1f245
- MakerPaymentSpent: 029c1643a3fcbeb60044315c294ee0831d40bc0053e1b2b1aba06c08ec0e5973
976b2efb5b894c3aaf15b9d05120b534e6f22ead4c6d27da3d97c32bf4d488c8
Both payments are on their chains and locked to the same secret hash 1730507198edea0cd39ed594f5ff65b37802961b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: dfa85518e6e04fe9ad41ac7118cef435518b18d7875970b0534c2ca911b97a7d
- TakerPaymentSent · TakerPaymentReceived: 976b2efb5b894c3aaf15b9d05120b534e6f22ead4c6d27da3d97c32bf4d488c8
- TakerPaymentSpent: 87f9b2b90af495a2a8d36bf0f6962a6d718565cd51a747866aadd600dc83b253
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.