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.
ef79c49bd2cbd3d2bb83c54a3875d4cacbf707e2b89352dfd2cc403be9ef6a48
Both payments are on their chains and locked to the same secret hash e9cb7ea45575309a7c80d59cd8ba89033a7b2423, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: ef79c49bd2cbd3d2bb83c54a3875d4cacbf707e2b89352dfd2cc403be9ef6a48
- MakerPaymentSpent: 592be885d76ecec3991c526e0d7e181ae432213535e4a021a0531ffac6465c44
90793cc7cf515e11ef288b8b0a8dea8738bac551adbf01c6a85ac296f415b093
Both payments are on their chains and locked to the same secret hash e9cb7ea45575309a7c80d59cd8ba89033a7b2423, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4e8f263c36d61bdece43a7eb04a4c50971dcaeadbcf0a7af31cb3a648f0ed14b
- TakerPaymentSent · TakerPaymentReceived: 90793cc7cf515e11ef288b8b0a8dea8738bac551adbf01c6a85ac296f415b093
- TakerPaymentSpent: b8f313feaa27aa8b82e4741172971908d70813b3a683d3a0e5c2170f4875241d
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.