Transaction | Address | Amount |
---|---|---|
0x0218...5d877a
|
0x0d50...df1270
|
-
0.007511966000780464 MATIC
|
0x0218...5d877a
|
0x1c58...2a7b27
|
+
0.007511966000780464 MATIC
|
0x0218...5d877a
|
0x1c58...2a7b27
|
-
0.007511966000780464 MATIC
|
0x0218...5d877a
|
0x4761...b78031
|
+
0.007511966000780464 MATIC
|
0x400d...683028
|
0xee53...c84857
|
-
0.002485443029487603 MATIC
|
0x400d...683028
|
0xe93e...44a02d
|
+
0.002485443029487603 MATIC
|
0xc3d4...5edc41
|
0x5ff1...6d2789
|
-
0.042010135210415736 MATIC
|
0xc3d4...5edc41
|
0x3d73...a86793
|
+
0.042010135210415736 MATIC
|
0xf738...5fa838
|
0xf6d1...ff67c6
|
-
11.8 MATIC
|
0xf738...5fa838
|
0xade1...36df65
|
+
11.8 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.