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.
024a32ecac345da6857ed1b20ec354515dfcea52d6f87b5b8dc61be7e4bc8f90
Both payments are on their chains and locked to the same secret hash e968c68b4bebb067aecc6bf7570fc1edc28aa45e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 024a32ecac345da6857ed1b20ec354515dfcea52d6f87b5b8dc61be7e4bc8f90
- MakerPaymentSpent: 3f7cb9f6a3fb9904cbb5f73afa8d8e26037d1674f6e08f87ff8ce4370c081b2c
3ec7151ad615870db05934656f8e2bc2d3afc46b578a55c005793a9308026700
Both payments are on their chains and locked to the same secret hash e968c68b4bebb067aecc6bf7570fc1edc28aa45e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0e0d155097b6799ba1b57c7dfb4b377c134a0f81ec821146e1c27b159a24aff7
- TakerPaymentSent · TakerPaymentReceived: 3ec7151ad615870db05934656f8e2bc2d3afc46b578a55c005793a9308026700
- TakerPaymentSpent: a96ea774ebbd09b14e3db1dd3e025df3882cd9b510d7836d593cd0bfd86bb5ba
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.