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.
ab1e5d8d8f320b4867cf27c26418e8865ce862d387ae69b002787397ed0e69fb
Both payments are on their chains and locked to the same secret hash 1d67456d661d8974d90c3d2d8a475b039428c1cf, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: ab1e5d8d8f320b4867cf27c26418e8865ce862d387ae69b002787397ed0e69fb
- MakerPaymentSpent: 4043329f94c2c48b88a3c67a649c2e37c143ac38bb07054d15ab1fd5e5f2d9ba
ee85ee24734e1f8c2bd604c447d214f9aad6a840772b184e63a47f9a81c6cdc7
Both payments are on their chains and locked to the same secret hash 1d67456d661d8974d90c3d2d8a475b039428c1cf, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4a087f257e8013f43ef88b37f58e43bfeaf3e1c0f1a9ef6941bed42c9cc2db6b
- TakerPaymentSent · TakerPaymentReceived: ee85ee24734e1f8c2bd604c447d214f9aad6a840772b184e63a47f9a81c6cdc7
- TakerPaymentSpent: 2577a05f31ad475a1a35e3b1bb195eccd20aeeb8244dad68254a40a5d2ba8116
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.