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.
7d07067677351f086590711de5b243e729e2a116877e57ffddc714a8c6ad8965
Both payments are on their chains and locked to the same secret hash 01eeb2fd8a8aa83fe09207afc2290f68a2707531, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7d07067677351f086590711de5b243e729e2a116877e57ffddc714a8c6ad8965
- MakerPaymentSpent: 41b1f9b0d5c9ea29454affb76f571f375b9681f278c144abe0a077757ccb75bd
2bc16141601e0f6da4cf351ff05e927c765f74581ad19338e983942b9a19a5ee
Both payments are on their chains and locked to the same secret hash 01eeb2fd8a8aa83fe09207afc2290f68a2707531, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5754009efcfdcb7d48330da4d51999a9595c308041a0727f37eab9aee8a113ef
- TakerPaymentSent · TakerPaymentReceived: 2bc16141601e0f6da4cf351ff05e927c765f74581ad19338e983942b9a19a5ee
- TakerPaymentSpent: bbda16e6954c6fb64ac346ee30abf0f2fff3c444d5a374f31c142672b30012fe
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.