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.
fd5bdbb257d7acba86a1e8fb8afa558585d747e585b00d2071f34fa1ab789d1b
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: fd5bdbb257d7acba86a1e8fb8afa558585d747e585b00d2071f34fa1ab789d1b
- MakerPaymentSpent: 7487695d79e7dbde2b3b27da29c3c784ef309c02745d83270fc39b9a7d9dfa3e
5a58e9b3c6ac3d0f22b301651aac84b0345d2897c90e4922f77f131567170b29
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeValidated · TakerFeeSent: aef255375ef544b08c9a3838952fbfe0eaa8d392ec4fc0f14fcdfdb449e43077
- TakerPaymentReceived · TakerPaymentSent: 5a58e9b3c6ac3d0f22b301651aac84b0345d2897c90e4922f77f131567170b29
- TakerPaymentSpent: ec4d7c364586d3d3ffa40e91ca9278a28f5032ffb2d2dd8f2ed00e338d33597b
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.