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.
0bfbd0bf522a000ffe313d54f55f456b7e04a55905ca614f84cd86c4890bcdc6
Both payments are on their chains and locked to the same secret hash b0df4688a94cb84008ef0ad56b15ae366296042b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0bfbd0bf522a000ffe313d54f55f456b7e04a55905ca614f84cd86c4890bcdc6
- MakerPaymentSpent: a7cc47e216708a5a008883aa03bbc5495545226f1d077eca35582c15cfa02fe0
a64e6aaee7dd94d6bb9f01088251f288536c5fbc49082af428ff900e6997bb03
Both payments are on their chains and locked to the same secret hash b0df4688a94cb84008ef0ad56b15ae366296042b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a06b91d1fb3716bab7f01c01700d079494af352c770d1d2d72772bb0102b249d
- TakerPaymentSent · TakerPaymentReceived: a64e6aaee7dd94d6bb9f01088251f288536c5fbc49082af428ff900e6997bb03
- TakerPaymentSpent: d47a8d4d2608dda9d7a08c82cacac876b0884396c4693cc5e0095368c736bfb7
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.