Transaction | Address | Amount |
---|---|---|
0x94ac...739ded
|
0x27be...1cc184
|
-
11.978967396493739704 MATIC
|
0x94ac...739ded
|
0x1111...960582
|
+
11.978967396493739704 MATIC
|
0x94ac...739ded
|
0x1111...960582
|
-
11.978967396493739704 MATIC
|
0x94ac...739ded
|
0x0d50...df1270
|
+
11.978967396493739704 MATIC
|
0x94ac...739ded
|
0x27be...1cc184
|
-
0.021032603506260296 MATIC
|
0x94ac...739ded
|
0xe51f...123e5e
|
+
0.021032603506260296 MATIC
|
0x5fa6...5cfd83
|
0x0d50...df1270
|
-
12.892832266715091192 MATIC
|
0x5fa6...5cfd83
|
0x1111...960582
|
+
12.892832266715091192 MATIC
|
0x5fa6...5cfd83
|
0x1111...960582
|
-
12.892832266715091192 MATIC
|
0x5fa6...5cfd83
|
0xaa54...e050fc
|
+
12.892832266715091192 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.