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.
3cbc3ddea6f43733a455110856eabd31f9ac8aeb8ab27b96f0f8adf8a4503294
Both payments are on their chains and locked to the same secret hash 0b65ba6ecc7575ea2d5ec390938cf7a37ffd808a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3cbc3ddea6f43733a455110856eabd31f9ac8aeb8ab27b96f0f8adf8a4503294
- MakerPaymentSpent: 2d9ace69da7b9142d4cde27a262fd7f0451988360b5f0786f046449bc3438f8c
ebbed1b7a1fcad237e609df98e89b5926bb981e5ce29fe3f71a4c9cf5a94c927
Both payments are on their chains and locked to the same secret hash 0b65ba6ecc7575ea2d5ec390938cf7a37ffd808a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: bb6e0cd8f4298a0dc5e008098ec7f2bc08e82b2597cc37fd1ef3be39ec9d3a8b
- TakerPaymentSent · TakerPaymentReceived: ebbed1b7a1fcad237e609df98e89b5926bb981e5ce29fe3f71a4c9cf5a94c927
- TakerPaymentSpent: 1d4b9247b54fe9cc7273af52f4c583ee9b30f83a9113154bb79a4db9300650f7
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.