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.
48750243911a4b97fd7cdc570e060d3f8c1a4bb1bfac19a53df83c808ebe452f
Both payments are on their chains and locked to the same secret hash c406c0bb4bed2b9b6d158fcaaa7961ea79ac0e1e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 48750243911a4b97fd7cdc570e060d3f8c1a4bb1bfac19a53df83c808ebe452f
- MakerPaymentSpent: ec269e2e49f091d8a11e0aa178bfb767e71b51c8b8c64bf7a9de60a716499b09
f964b3308fae973c34ac93befe6200e0f9d2be18e0d230cb70f52e29972d919d
Both payments are on their chains and locked to the same secret hash c406c0bb4bed2b9b6d158fcaaa7961ea79ac0e1e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9489db6cde89e1dcf5d25d8d05a44c1185b49e2c3c8840381af31120d133ee66
- TakerPaymentSent · TakerPaymentReceived: f964b3308fae973c34ac93befe6200e0f9d2be18e0d230cb70f52e29972d919d
- TakerPaymentSpent: 4aa39736c4a271bf2eb42eae7b9b89a01c8e53525794cc9daec66c4c71be90b3
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.