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.
8351331e88119ff0a0306315c0149396a5b72c878dd9c784a46ff16770042224
Both payments are on their chains and locked to the same secret hash 71f1e5e1b735618c7b1058bb8915685a1acebc2a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8351331e88119ff0a0306315c0149396a5b72c878dd9c784a46ff16770042224
- MakerPaymentSpent: efee599a6f4e18e7de6797cd23407616d2e52707b59ade49fb892d436414f766
29b969c6b03b2912e2e9a02a13fb58b4f420f7bd6e8dffbe0ae37be8c56cb2ac
Both payments are on their chains and locked to the same secret hash 71f1e5e1b735618c7b1058bb8915685a1acebc2a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 52a8269b2aeef36c03fddb63f556c887d8f6c1fd5ea1b5835fb7bb6ee1c9f4bd
- TakerPaymentSent · TakerPaymentReceived: 29b969c6b03b2912e2e9a02a13fb58b4f420f7bd6e8dffbe0ae37be8c56cb2ac
- TakerPaymentSpent: 442323590255b3e2c38daee99322d6ad611a4f4da133193ba9b25e79df7aa296
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.