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.
7f8560353a67f81d130c6afc6d55c06090c2ab9e20c6a1edc1110194336c8546
Both payments are on their chains and locked to the same secret hash 2cf14cdca0de759bac695fc0387e0fcdf9f1bea8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7f8560353a67f81d130c6afc6d55c06090c2ab9e20c6a1edc1110194336c8546
- MakerPaymentSpent: 4ee7f4a85951359f3ea201de08282841b4ffb71b65c9446ef17e7ebee2483927
4caaaecbccc657ca555ac0b2a62153f9697c89274c05308a30f101bd4c7725a1
Both payments are on their chains and locked to the same secret hash 2cf14cdca0de759bac695fc0387e0fcdf9f1bea8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 33ec89d2a7b75d971dd285c64df32bfec096f79188af4cf7fa731696324f995f
- TakerPaymentSent · TakerPaymentReceived: 4caaaecbccc657ca555ac0b2a62153f9697c89274c05308a30f101bd4c7725a1
- TakerPaymentSpent: cb93c5ae81f276989763668cf1f5c2559d7eb8fb56d512b8c4d012b8532ba08f
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.