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.
4656e5599a66f00b6a3c8493c819e4eaef8eb7656fafc8cadb89f4a13afd8744
Both payments are on their chains and locked to the same secret hash 6e8c8d8815c95011be477939f27f595e76ba69c2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 4656e5599a66f00b6a3c8493c819e4eaef8eb7656fafc8cadb89f4a13afd8744
- MakerPaymentSpent: 209e2bd91900adce1b9b4c390ea5aadfd26728c4e4af1a759f053884090dc10b
2d8ecbb3c08aabb366c9d4c2730a42745bb18b2829ef4b0eeb562556c7d28d57
Both payments are on their chains and locked to the same secret hash 6e8c8d8815c95011be477939f27f595e76ba69c2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9a2acadfd4feb6c69dbe8eeca9dac230d922b27025d27ad02b7b302e1c562c80
- TakerPaymentSent · TakerPaymentReceived: 2d8ecbb3c08aabb366c9d4c2730a42745bb18b2829ef4b0eeb562556c7d28d57
- TakerPaymentSpent: 7bc3031f5088e2bf4b26f8634a181ee7ea20635c1d15b83e0f1fce1d6ee18689
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.