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.
cf446d561db126dc452edab1c284cc55c9374ce0b75aba6e50fe4a2aee012e0f
Both payments are on their chains and locked to the same secret hash b8eb363c0f8a88cbe15cb7630f75ea16d4e755ac, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: cf446d561db126dc452edab1c284cc55c9374ce0b75aba6e50fe4a2aee012e0f
- MakerPaymentSpent: 73ed8702841f0f247285261e42386b5c90996748c6e0f37e6af394cf4d20da80
d64478933633736d157fbcb814d5739f03d49bab54be406c6bc4e6ccc9ab1096
Both payments are on their chains and locked to the same secret hash b8eb363c0f8a88cbe15cb7630f75ea16d4e755ac, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c3f0fe8e5ab359db2afa62cab48d3632c85e55da415854a3aaf300d2da0b59c0
- TakerPaymentSent · TakerPaymentReceived: d64478933633736d157fbcb814d5739f03d49bab54be406c6bc4e6ccc9ab1096
- TakerPaymentSpent: 6c6ee94cc7c80901d2476ab87e34a5dee8151f3d83fe6e2807e74694f1d81d46
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.