Transaction | Address | Amount |
---|---|---|
0xfa45...5699e8
|
0x647e...639267
|
-
0.007034485184189017 MATIC
|
0xfa45...5699e8
|
0x7e08...43d521
|
+
0.007034485184189017 MATIC
|
0x3f99...7244c4
|
0x647e...639267
|
-
0.030277789402645472 MATIC
|
0x3f99...7244c4
|
0x7e08...43d521
|
+
0.030277789402645472 MATIC
|
0x5ded...e110bf
|
0x5ff1...6d2789
|
-
0.021281546344760268 MATIC
|
0x5ded...e110bf
|
0x3d73...a86793
|
+
0.021281546344760268 MATIC
|
0x4281...f5e166
|
0x0d50...df1270
|
-
0.003815535377065777 MATIC
|
0x4281...f5e166
|
0x19a5...996198
|
+
0.003815535377065777 MATIC
|
0x4281...f5e166
|
0x19a5...996198
|
-
0.003815535377065777 MATIC
|
0x4281...f5e166
|
0xcace...a7c8ba
|
+
0.003815535377065777 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.