Transaction | Address | Amount |
---|---|---|
0x4c91...5d2f21
|
0x5ff1...6d2789
|
-
0.02094215889676131 MATIC
|
0x4c91...5d2f21
|
0x3d73...a86793
|
+
0.02094215889676131 MATIC
|
0x5fac...fb3b95
|
0x5ff1...6d2789
|
-
0.036857828484449349 MATIC
|
0x5fac...fb3b95
|
0x7a81...4bf876
|
+
0.036857828484449349 MATIC
|
0x0532...ddc49b
|
0x5ff1...6d2789
|
-
0.02094215889676131 MATIC
|
0x0532...ddc49b
|
0x2ce3...0bdfd8
|
+
0.02094215889676131 MATIC
|
0x8a79...c414f1
|
0x0e53...0b979a
|
-
0.713944444444444444 MATIC
|
0x8a79...c414f1
|
0xfc07...e0128d
|
+
0.713944444444444444 MATIC
|
0x8a79...c414f1
|
0x0e53...0b979a
|
-
6.425499999999999999 MATIC
|
0x8a79...c414f1
|
0xcaf5...bd002d
|
+
6.425499999999999999 MATIC
|
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.