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.
0191ed67f11237d91252f5d2f55322f05fee2d146a1cf467f0c31c8cce9f47e5
Both payments are on their chains and locked to the same secret hash 47cac9dd405ed193805c806287a1a978e5370f20, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0191ed67f11237d91252f5d2f55322f05fee2d146a1cf467f0c31c8cce9f47e5
- MakerPaymentSpent: 35a0235f62b96af5a81ceb7f67ff0722d74746052f2c96c912e0e427549983eb
31a792ddbed33a82cc6abedde7404d3bc240fd82d0ff7376fe9c0c9214779051
Both payments are on their chains and locked to the same secret hash 47cac9dd405ed193805c806287a1a978e5370f20, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f9db13c9bc05bd6e824daf972324b9e77da206e3a15fe576968b090b586a470a
- TakerPaymentSent · TakerPaymentReceived: 31a792ddbed33a82cc6abedde7404d3bc240fd82d0ff7376fe9c0c9214779051
- TakerPaymentSpent: d0af9307321fac3846c60234b45f0b516d9c3480ab86eb4cb7f4de93d8ce0f82
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.