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.
0fdfcf24825d30800866076763fe6b8d96fd296fcb46e97dfdee1656112f1205
confirmed on-chain, calling the swap contract, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 0fdfcf24825d30800866076763fe6b8d96fd296fcb46e97dfdee1656112f1205
- MakerPaymentSpent: 6c371d05f0e2fa8a8add6201676c460c63d95b6b63d5c9880809cd3167b8ee08
e7de3d28275d29628264604d934177e7029659be618a00523324f3de8679abdf
ARRR settles as ZHTLC, whose transfers do not appear as an output any chain server can read, so the transaction the record names cannot be checked against a chain here
- TakerFeeSent · TakerFeeValidated: 1e800473275a297891b8eb0d575a287c2973011d22b2ae635753c24935d2329d
- TakerPaymentSent · TakerPaymentReceived: e7de3d28275d29628264604d934177e7029659be618a00523324f3de8679abdf
- TakerPaymentSpent: eb815d4d4e4cbc342f73dab04af2d9352391498d9e59de36a41cf6d0ab897b5e
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.