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.
0eb60285e5312b3c0e8089a2e80f3402e4f76baf04b796649b09485648a93d8e
Both payments are on their chains and locked to the same secret hash bb050c02e5b63def8d7217d063f7c480ace7a69d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0eb60285e5312b3c0e8089a2e80f3402e4f76baf04b796649b09485648a93d8e
- MakerPaymentSpent: 6f27ca98a25dd2709a705d14c8e930b19c2681a2d4ddd96e7bbe9119991589e5
f3cbd3c7546b545f132fc4990c52143a50040bb36001da89884a6eb202c38590
Both payments are on their chains and locked to the same secret hash bb050c02e5b63def8d7217d063f7c480ace7a69d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: cc0236a61d002d80caf28d5db07b0870e5e6c5a3a7937a163d4c5075e40f5666
- TakerPaymentReceived · TakerPaymentSent: f3cbd3c7546b545f132fc4990c52143a50040bb36001da89884a6eb202c38590
- TakerPaymentSpent: 72b39aaf071ce1d54e2560d6cfaeaf17e7afa18030839a737ade6272eed5abba
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.