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.
a7a749a12fee3d0a76f3e2e853915b17e24e68e0a135401252cfc09cdf735a54
Both payments are on their chains and locked to the same secret hash 19164666b00b1e1c0d1cab6ef7f2d4682a968ab8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a7a749a12fee3d0a76f3e2e853915b17e24e68e0a135401252cfc09cdf735a54
- MakerPaymentSpent: 83f10714eb2c0c73daa54fa2ae59a9d79ff7449f0c594168713b4ad54aef6517
edc7db09290664082106a5ac091a46e249bd99ce68784ab6054a07429c176512
Both payments are on their chains and locked to the same secret hash 19164666b00b1e1c0d1cab6ef7f2d4682a968ab8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 116a871c5990b1bb1ec3e22ff094405799f9ea49c8b6520bde97db255bd28c6d
- TakerPaymentSent · TakerPaymentReceived: edc7db09290664082106a5ac091a46e249bd99ce68784ab6054a07429c176512
- TakerPaymentSpent: 8f696994fa9c96f70491ebda4010cc8362ef6604c8bbe1e31538608e05b659c2
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.