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.
75038e8108465a17771c23d1cf398f41261169c0c04a41793fbb9c4836f7b798
Both payments are on their chains and locked to the same secret hash cd38103aa6c9bfa74bbc867050400889daf0b848, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 75038e8108465a17771c23d1cf398f41261169c0c04a41793fbb9c4836f7b798
- MakerPaymentSpent: 45dc0b4055df319eecacf075514fb206950aa4b57b49c8c17b4ba8fef837e2e0
f5efea1efe89af4edba86406c4d072b31cabb25aa53e4a0ac46045957c2c1654
Both payments are on their chains and locked to the same secret hash cd38103aa6c9bfa74bbc867050400889daf0b848, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: a2771002612cfaf443d3a538fd31df847a3f01df7820012c4dd9afbbce461904
- TakerPaymentSent · TakerPaymentReceived: f5efea1efe89af4edba86406c4d072b31cabb25aa53e4a0ac46045957c2c1654
- TakerPaymentSpent: 38ef92ab83f12567497d08aef765b837912800a96bc184a1130c6bfd2d09c1af
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.