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.
175f5f9f84b742117c48a2631b911165353d4a3a6230bef2b5e86d658aa241d3
Both payments are on their chains and locked to the same secret hash 7362df92e6c71f883e50bdaafb8e5fa261bb7dc2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 175f5f9f84b742117c48a2631b911165353d4a3a6230bef2b5e86d658aa241d3
- MakerPaymentSpent: 0fab8de018e6539c466cc7f0fa7970b710f78a964b08687ea1a02d75780336df
b1583712c01cc19383ac0ddf05a83beaf619f8a01a036d9b2eb5a4b077d4543f
Both payments are on their chains and locked to the same secret hash 7362df92e6c71f883e50bdaafb8e5fa261bb7dc2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 71e2c98939801349e68f7e024220c870c984ca497ed324d5ac1fc620680a4dea
- TakerPaymentSent · TakerPaymentReceived: b1583712c01cc19383ac0ddf05a83beaf619f8a01a036d9b2eb5a4b077d4543f
- TakerPaymentSpent: 16cfd2fa8b7ee40f6abc6e1aa2743b6262b0405bada442ded19f4761b243868f
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.