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.
0412c2c060ce83d313e19a40d739dc58326d114fde32e74a1239a1be13bab543
Both payments are on their chains and locked to the same secret hash ab7fd01f5e31004296bdbb1c4849a3832446ade5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0412c2c060ce83d313e19a40d739dc58326d114fde32e74a1239a1be13bab543
- MakerPaymentSpent: 56ddcfeb86efa56c2bfbf6a771ded2c7a2d52e69b1fb197924c95059af1fd029
f2f13bd9314eaa7db41fec22a3216c70edad67c9013b7a5a025642eb0ef0ff7b
Both payments are on their chains and locked to the same secret hash ab7fd01f5e31004296bdbb1c4849a3832446ade5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7d016a2b68ec34101b33dc5aa31c5cd1e83ab9b8e52ffdafcff28e61caca0501
- TakerPaymentSent · TakerPaymentReceived: f2f13bd9314eaa7db41fec22a3216c70edad67c9013b7a5a025642eb0ef0ff7b
- TakerPaymentSpent: 0f3737efa35dd86cb72e90bdfe4d4b675ebfec26c3c0241d5e5119d5f279f663
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.