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.
744af35bbeb66c40829b5ae22acad8cdb3e62ec7ce4e51739b1663d8bc757952
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 744af35bbeb66c40829b5ae22acad8cdb3e62ec7ce4e51739b1663d8bc757952
- MakerPaymentSpent: beb7c0d283b8cb43fd34c5d5793835e5662c6e85930fc75186c53dcaf4ef49db
5160dd2eb9e0afcba306fc89cd62ff880b77bc95003b9f022b0a102d3c37527a
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeSent · TakerFeeValidated: 0aeed4cff36363043a186247b243dbba12b584d0cee626c1655d55ba23e300a6
- TakerPaymentSent · TakerPaymentReceived: 5160dd2eb9e0afcba306fc89cd62ff880b77bc95003b9f022b0a102d3c37527a
- TakerPaymentSpent: 9a9bed01a75bda0c6dd31b7e3644b64f80d5261a424f8b5993c3fca66ef10a60
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.