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.
3fc9cd80b221a04dc86be6049967ae89f3c02b85fb1d5456716f4dd68508124c
Both payments are on their chains and locked to the same secret hash bce0ed7ae96744d00fdf5a06a0bccdddd671d2be, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 3fc9cd80b221a04dc86be6049967ae89f3c02b85fb1d5456716f4dd68508124c
2a234c1171edad6ab317ea9d1839170f8ff2c1de7a171a8580d2fa1c9a37cd24
Both payments are on their chains and locked to the same secret hash bce0ed7ae96744d00fdf5a06a0bccdddd671d2be, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · a735abefa980aa957153c2d958443ea2ce20e01bf26d2cf7d2e1be265c72635a
- TakerPaymentReceived · 2a234c1171edad6ab317ea9d1839170f8ff2c1de7a171a8580d2fa1c9a37cd24
- TakerPaymentSpent · d521545f2e4d066e7682e10bd8d3b9c98d7a12a1b8feacbd4b4ceb0838efc841
No anomalies were recorded against this swap.
Reported by kdf-statsdb.