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.
112c3b49955bb413377dfc8229d1f18f6702aba8920883188e3374544cb46dcc
Both payments are on their chains and locked to the same secret hash a30e780c0f5f76834f02b428baea7188285a508c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 112c3b49955bb413377dfc8229d1f18f6702aba8920883188e3374544cb46dcc
- MakerPaymentSpent: 49514999ac66a39be89658daf143191b0f5818b1b3590fca7fb7663910bd584e
ba50a5ac97f3d1039386bac348614d6a4cfe6a7c3017fe08e4ce16d776f2d662
Both payments are on their chains and locked to the same secret hash a30e780c0f5f76834f02b428baea7188285a508c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 03e23e9d1ad2c865daf2666411660bc6bbccb970a11fe3d3f839613f054c1e01
- TakerPaymentSent · TakerPaymentReceived: ba50a5ac97f3d1039386bac348614d6a4cfe6a7c3017fe08e4ce16d776f2d662
- TakerPaymentSpent: a9068b065eb16ec6ec1ae7da0961c1e5009bbeca2c54bf30393d7c9010d68a04
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.