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.
070e89e43a1df7210f61942245066973c4681d230d1850531e9034659b3460ae
Both payments are on their chains and locked to the same secret hash 1adcef19bec3e818f0f0474b496833401bdfc2b4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 070e89e43a1df7210f61942245066973c4681d230d1850531e9034659b3460ae
- MakerPaymentSpent: 862e60b2a481cb3c6915f5360943348a17b11a4c943207ef97ea07aa2048db38
ddccc12d12d638aa0fd930c8ec44dcbe7e0efc0b95408350c8324689cb75e2ec
Both payments are on their chains and locked to the same secret hash 1adcef19bec3e818f0f0474b496833401bdfc2b4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 4dd74e95c538531c9d9fea189216343300cffc15997398426efee648131e6ee8
- TakerPaymentSent · TakerPaymentReceived: ddccc12d12d638aa0fd930c8ec44dcbe7e0efc0b95408350c8324689cb75e2ec
- TakerPaymentSpent: 6fec16b7f8f1671a5a39b6944fc481d3fd330ab2d7dc9f54554776616a13cb85
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.