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.
04684ec31d31c5628d157c56f53c1cf8c006034fa6f447b25b2dfbee1de8a47b
Both payments are on their chains and locked to the same secret hash dd42061cadbf05d5bfa0c302b71c84d8b24d24f0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 04684ec31d31c5628d157c56f53c1cf8c006034fa6f447b25b2dfbee1de8a47b
- MakerPaymentSpent: 210873d3b776a0fb30914c5f2c0bd7019b651338a4370422b2cc3ce3e293c4d9
c7351ff9c0e0681e43d0a335adcba14b7c82000506294e8030ebdc5b24647af7
Both payments are on their chains and locked to the same secret hash dd42061cadbf05d5bfa0c302b71c84d8b24d24f0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3c4ba30df4c55ffac53b914dfc6fb60bb83d9d1d7ba32fa9ce474c01fd9f0419
- TakerPaymentSent · TakerPaymentReceived: c7351ff9c0e0681e43d0a335adcba14b7c82000506294e8030ebdc5b24647af7
- TakerPaymentSpent: 56aa1783f00eae065828b77b16909e1f65e816bdf026006c53f67db3cd38970a
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.