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.
d065b7f5846ed10a79eac65c582cee25f8c89b1d21373f39d62bf6f057422c77
Both payments are on their chains and locked to the same secret hash 5647d048420176d210255fc89bccaffb1dca0d56, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d065b7f5846ed10a79eac65c582cee25f8c89b1d21373f39d62bf6f057422c77
- MakerPaymentSpent: 0bf7922437f5f234fb045f80d332020a078565fce2cc7c4163a66271e7547409
f1fb22ddf1a6d4d4de474378fad8ff9def1a0a57e29082623090b366d379c746
Both payments are on their chains and locked to the same secret hash 5647d048420176d210255fc89bccaffb1dca0d56, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 224cef82515528279fea70e475a23e394232bb526ac640a1f8bef61404638798
- TakerPaymentReceived · TakerPaymentSent: f1fb22ddf1a6d4d4de474378fad8ff9def1a0a57e29082623090b366d379c746
- TakerPaymentSpent: 6cc2896e20d1055b7fee3de82979413d44cfdcb8f363274caad4a77fc0352e80
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.