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.
23ce31723e1e58fb155494825fc54e6d9057776328239cec8ae46796216cac20
Both payments are on their chains and locked to the same secret hash ca0773d9b18f9527b826d4b368f41a751c70b0f6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 23ce31723e1e58fb155494825fc54e6d9057776328239cec8ae46796216cac20
- MakerPaymentSpent: 37308751f6702b8c3c5f35dcf79303756f06cc29ccb55613cffa054a4a1cc64d
4023d0922fab94fa7b2867604b7efc052599682e555c0dbc8727c191438b09dc
Both payments are on their chains and locked to the same secret hash ca0773d9b18f9527b826d4b368f41a751c70b0f6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2373c0fa99b2febb587060a63bc27957d04b8b7cd64c0bd740158ddac7481ed6
- TakerPaymentSent · TakerPaymentReceived: 4023d0922fab94fa7b2867604b7efc052599682e555c0dbc8727c191438b09dc
- TakerPaymentSpent: faff9ccbf5b206956ab76732c121e3397e58c016ddaa5dde75cec572ed3ee612
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.