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.
4a7f73076b7482671d046c11ab2ed2d1433304ce4a43463dbf04fb9541e1763b
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 4a7f73076b7482671d046c11ab2ed2d1433304ce4a43463dbf04fb9541e1763b
- MakerPaymentSpent: e44452d5d24133de3aa261e3980dc79729c9fb9bd635039664705cb554ba1fee
4d9e97d4603af64dd5434511fd2058e0f49f1afef2b030df71a0a0abd59e2028
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeSent · TakerFeeValidated: 5ac423617bd7a75e5233435a613eec35ab2c2cedae81d6399a703cc6208a4ec9
- TakerPaymentSent · TakerPaymentReceived: 4d9e97d4603af64dd5434511fd2058e0f49f1afef2b030df71a0a0abd59e2028
- TakerPaymentSpent: 333b475548a94535af061584ec99ad82ff90ea3fbea1de98edf4989d01c9490b
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.