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.
34275e6d09e7ff35066b81a8679f91081dc2121b5d05eac0d0710f722e6c6db2
Both payments are on their chains and locked to the same secret hash 3ff46e812ec8346644bc523cb6cc2faac0e446c3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 34275e6d09e7ff35066b81a8679f91081dc2121b5d05eac0d0710f722e6c6db2
- MakerPaymentSpent: 8a33a8b72ce21607d333219829b2abfb667183635c02a73489d64dbf8daa833d
a6dceddbe826162583d2b0b528133a97142e60039d674df587a7392c9b05afb9
Both payments are on their chains and locked to the same secret hash 3ff46e812ec8346644bc523cb6cc2faac0e446c3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a27505c2b6a2d6ec06584620260def81a3522a269d34a922edf42b1c8c423fe4
- TakerPaymentSent · TakerPaymentReceived: a6dceddbe826162583d2b0b528133a97142e60039d674df587a7392c9b05afb9
- TakerPaymentSpent: dd4de8db4b30aefb3987f425e57359cf2f8f030c87eb9b62e9fdb2ae80226e28
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.