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.
8f62887442077a3c07c6024c1e54ca7a7d9d0339c74e71cb6eb0eff00bcce68b
Both payments are on their chains and locked to the same secret hash e820b0eee91b622afbc237667911cb4e354603ed, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8f62887442077a3c07c6024c1e54ca7a7d9d0339c74e71cb6eb0eff00bcce68b
- MakerPaymentSpent: ba996701967c92931702e47a75288389d13c3ea208801790b092377337c6f4fd
e4c57622897258069a3f8ec2ba5464b9b40c839878b156f85881b6d145761461
Both payments are on their chains and locked to the same secret hash e820b0eee91b622afbc237667911cb4e354603ed, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 66ae09134a12aa7e2e0212db4c79ac62f0a747c029eaafdea2894bf633850bea
- TakerPaymentSent · TakerPaymentReceived: e4c57622897258069a3f8ec2ba5464b9b40c839878b156f85881b6d145761461
- TakerPaymentSpent: 291a606d17336eb13d4818e227f26c9cc728cc16cd66164c754a68df0a75af60
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.