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.
7ee232082d863b4d5d6dd47e941a47d92fac4c2539b60d61919b5ee0bf9e2fe5
Both payments are on their chains and locked to the same secret hash 56fc61d8435a77d8580f90748bc362f96f5aaa8d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 7ee232082d863b4d5d6dd47e941a47d92fac4c2539b60d61919b5ee0bf9e2fe5
- MakerPaymentSpent: fddd2cc9911bcc448a9dce0e1762784dbd67784ca6980e0d1baf9f4013801002
382cccf1e6ade74c397baf67dfa24e89b55a88073d16d0c33bc5653621791471
Both payments are on their chains and locked to the same secret hash 56fc61d8435a77d8580f90748bc362f96f5aaa8d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3be47d0bddebc40b536eebc1b4bfc37c835e58a541c64adff89746cb622d0430
- TakerPaymentSent · TakerPaymentReceived: 382cccf1e6ade74c397baf67dfa24e89b55a88073d16d0c33bc5653621791471
- TakerPaymentSpent: a81aeb64eb77939868ace67f623cae3cc0b99ea1b286538eb282a37150230671
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.