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.
dfe9b01f5d7e25f67e2ee98bedad17e8cc319d1b54ec2b474eec227635f4e083
Both payments are on their chains and locked to the same secret hash 5600da45999681357e03ff0ce0fc13fc0f38b509, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: dfe9b01f5d7e25f67e2ee98bedad17e8cc319d1b54ec2b474eec227635f4e083
- MakerPaymentSpent: 842c87396ecb149245ebf282673a1e7a8dc31f9367e1b8583656da4f4366894d
8568169bff1a51d7c0d4bf1ab4815f8ff236bde170bf493526fae546b4de04b4
Both payments are on their chains and locked to the same secret hash 5600da45999681357e03ff0ce0fc13fc0f38b509, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 5438e06aa685285ba391f03b6644b94990c219463666da2004455e0a70a8064a
- TakerPaymentSent · TakerPaymentReceived: 8568169bff1a51d7c0d4bf1ab4815f8ff236bde170bf493526fae546b4de04b4
- TakerPaymentSpent: 1d9f666dc366478df37230fa98ca64003934d34745c900bdb9ec5efafcdca9c8
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.