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.
92f77735b908561949e1444446d254c21038161554ffd9839ce22eabec9d618a
Both payments are on their chains and locked to the same secret hash 4f0ca0358983db8856884f5b2f3708a6c7e5718f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 92f77735b908561949e1444446d254c21038161554ffd9839ce22eabec9d618a
- MakerPaymentSpent: 57483a9c860c614fbbb1902fff117174e5ebf79cd8554b7d6cfe1264863b0d83
2c4efbfc34716e2908879e6979b537849b9226f13f45a152559cac84fd4caeef
Both payments are on their chains and locked to the same secret hash 4f0ca0358983db8856884f5b2f3708a6c7e5718f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2ca48b23a62ce8f3d53c927417b113f60cf85adc17a8d8cea0a02da7b8efe9ae
- TakerPaymentSent · TakerPaymentReceived: 2c4efbfc34716e2908879e6979b537849b9226f13f45a152559cac84fd4caeef
- TakerPaymentSpent: a80d69a03c7ad002860bd818a6bba2b74123cb4f4595f64746525242f931b00f
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.