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.
be9e4fd431461f61e1c2c746cdc3747d23ec6e53c11c8f5617ae839955ce18f8
Both payments are on their chains and locked to the same secret hash b44e80e60e0acb2567874ed72260d0230bd078a5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: be9e4fd431461f61e1c2c746cdc3747d23ec6e53c11c8f5617ae839955ce18f8
- MakerPaymentSpent: 58c7fd3cb8627e9d32410e4245957d3406f4cd7f69138ec47d5188aa54faad6c
fd46ec4f86c6a3322a698a9addb62b5c597aed6813d6f147fc0e2df44134a1c9
Both payments are on their chains and locked to the same secret hash b44e80e60e0acb2567874ed72260d0230bd078a5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 63415628b73d80a9253d9fbd8651d183190b9a5b72f2af66701e64806fc433f5
- TakerPaymentSent · TakerPaymentReceived: fd46ec4f86c6a3322a698a9addb62b5c597aed6813d6f147fc0e2df44134a1c9
- TakerPaymentSpent: 62800bdf7c38cced470fd2157bd9df56719c6ccec7b93a70679791bf6e8603b8
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.