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.
4061c965e363d1d9d5f6e8cbb7928b05db58849a8012b1084b28058eaff6b3ff
Both payments are on their chains and locked to the same secret hash 257fc204b2fd3d354b7ac3dea70bcf9835a828fc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 4061c965e363d1d9d5f6e8cbb7928b05db58849a8012b1084b28058eaff6b3ff
- MakerPaymentSpent: 1d3ef48bd1b77320e5cab927004db99411b6cd03355387951d7fbf4b2b85a9ce
af2af1dfe37a4e37d78e013aca298f0972e493b0837ae0a345a99800cd033498
Both payments are on their chains and locked to the same secret hash 257fc204b2fd3d354b7ac3dea70bcf9835a828fc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: dd944ccc69c7fe84ddfa5e3d949b589854a1edfdf598980dbf4811610350602e
- TakerPaymentSent · TakerPaymentReceived: af2af1dfe37a4e37d78e013aca298f0972e493b0837ae0a345a99800cd033498
- TakerPaymentSpent: f5da434bebfffb6a945ddac8bbee85b625a8ba63ec804d408349e37281ed48b5
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.