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.
8927649861f6ce3274da5441df396d2d449627746881e410694b9dfd14f31eee
Both payments are on their chains and locked to the same secret hash 6384ad88c673b25ca5b0693906092b7e01029ae8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8927649861f6ce3274da5441df396d2d449627746881e410694b9dfd14f31eee
- MakerPaymentSpent: fa11e9b0a21acfc2bbdd90b3c5ee22f093ad8d44dd69b78e32509dd92a4d100f
befa472dd4988f40016ae8006d7437028fe27f5988c20637c2847b64621c19dd
Both payments are on their chains and locked to the same secret hash 6384ad88c673b25ca5b0693906092b7e01029ae8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 32a0eb243a3e05c01a569c329ae1cd8daf88cb758d59a82041c0a3a4098f2517
- TakerPaymentSent · TakerPaymentReceived: befa472dd4988f40016ae8006d7437028fe27f5988c20637c2847b64621c19dd
- TakerPaymentSpent: 5f38ddd8f22f0d970a3c31c5ccc3672c90c57e6f8a56ef8234baec3ec8ac3aa2
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.