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.
db59faae688ed3aaae07575c874f5c8a04c5c33402813bf83ec7939c1c336b70
Both payments are on their chains and locked to the same secret hash 1918ee66110d1cb04e11395119e6733db2c2a014, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: db59faae688ed3aaae07575c874f5c8a04c5c33402813bf83ec7939c1c336b70
5bd671b8ab8a63fd7c60464874cac1173991c7351c4932f6b286890ec3a70273
Both payments are on their chains and locked to the same secret hash 1918ee66110d1cb04e11395119e6733db2c2a014, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: d98526edbcff106a49f8b99692b2a48f4e7ed36cc8a2a79e23ce68e306805098
- TakerPaymentReceived: 5bd671b8ab8a63fd7c60464874cac1173991c7351c4932f6b286890ec3a70273
- TakerPaymentSpent: 6583a0c5667f93f27c77dd9a9f507a79b04cd8e2c237a7f78e8fa3cf0b574463
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.