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.
be40266ed5faa2e08887521d28e9c968a6702d0e60769fa7590b9a7a1a7ff311
Both payments are on their chains and locked to the same secret hash 2241804f7420255bf13d27f12f533244e63524d1, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: be40266ed5faa2e08887521d28e9c968a6702d0e60769fa7590b9a7a1a7ff311
- MakerPaymentSpent: c42633a3261671699e3ac27f063204d2a9abf9ee1812b142906768efd9bf3340
9125f1e54cca25f4fbc08b720ab53e35013cf7134da6e842ba761f531fc58235
Both payments are on their chains and locked to the same secret hash 2241804f7420255bf13d27f12f533244e63524d1, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: e35bb28ce19ec3c0939a64dcdb08da89829ac19c0e2dacfedd8dd0463df10bd7
- TakerPaymentSent · TakerPaymentReceived: 9125f1e54cca25f4fbc08b720ab53e35013cf7134da6e842ba761f531fc58235
- TakerPaymentSpent: 757660f11216c041e10fa29d4fe4ba1da31319a9d27f9d0d854003960b92b38f
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.