Transaction | Address | Amount |
---|---|---|
0xfdb1...5b0a15
|
0x25fb...dae174
|
-
0.006325270372751133 WETH
·
24.67 USD
|
0xfdb1...5b0a15
|
0x5ff9...69bf45
|
+
0.006325270372751133 WETH
·
24.67 USD
|
0xfdb1...5b0a15
|
0x5ff9...69bf45
|
-
0.006322228279826048 WETH
·
24.66 USD
|
0xfdb1...5b0a15
|
0x0c78...d35bb2
|
+
0.006322228279826048 WETH
·
24.66 USD
|
0xfdb1...5b0a15
|
0x0c78...d35bb2
|
-
0.06656723776980185 AAVE
|
0xfdb1...5b0a15
|
0x25fb...dae174
|
+
0.06656723776980185 AAVE
|
0xfdb1...5b0a15
|
0x5ff9...69bf45
|
-
0.000003042092925085 WETH
·
0.01 USD
|
0xfdb1...5b0a15
|
0x1869...7a17bd
|
+
0.000003042092925085 WETH
·
0.01 USD
|
0x1b1b...58f2ff
|
0x0830...23c66d
|
-
1.114188 USDC
·
1.11 USD
|
0x1b1b...58f2ff
|
0xe485...d6f433
|
+
1.114188 USDC
·
1.11 USD
|
Polygon experiences an hour-long outage due to a consensus bug shortly after a major hard fork upgrade.
Polygonscan's outage on July 30 led to confusion, but the Polygon network remained stable as developers assured it was fully operational.
Polygon's Heimdall V2 experienced an outage causing temporary network disruptions, but the Bor layer remained operational.