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.
024e065d995feef6aeb6ecd5fe3d1f37017992dec6fb988ac82713e30aacd466
Both payments are on their chains and locked to the same secret hash c21e4dd494e3354551b02c36c38b0eb792d8c815, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 024e065d995feef6aeb6ecd5fe3d1f37017992dec6fb988ac82713e30aacd466
- MakerPaymentSpent: 797a60b1b40f4eef48d75928d06547953578edfc5c3b3e17040abde7f51f33f2
6933f39bf146e0b46caff3755eeec373c03a0a55c17fd6787f9523d42eda7dac
Both payments are on their chains and locked to the same secret hash c21e4dd494e3354551b02c36c38b0eb792d8c815, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0a5fd3f05c32bbae339f92cb799016de67791324053e7d7599e687dc2baa5f2f
- TakerPaymentSent · TakerPaymentReceived: 6933f39bf146e0b46caff3755eeec373c03a0a55c17fd6787f9523d42eda7dac
- TakerPaymentSpent: 8cce236302463798dcdd53ce726bdc431f5fc96ec7e2c250a01e5a61be9bf547
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.