Transaction | Address | Amount |
---|---|---|
0x72f4...6076f0
|
0x7b36...c6115d
|
-
0.099482690011937915 MATIC
|
0x72f4...6076f0
|
0x23e8...603a6c
|
+
0.099482690011937915 MATIC
|
0x72f4...6076f0
|
0x7b36...c6115d
|
-
19.896538002387583 MATIC
|
0x72f4...6076f0
|
0xb6ea...c2b52a
|
+
19.896538002387583 MATIC
|
0x72f4...6076f0
|
0xb6ea...c2b52a
|
-
19.896538002387583 MATIC
|
0x72f4...6076f0
|
0x0d50...df1270
|
+
19.896538002387583 MATIC
|
0x7aa6...0fc274
|
0x0d50...df1270
|
-
18.901711102268203 MATIC
|
0x7aa6...0fc274
|
0xb6ea...c2b52a
|
+
18.901711102268203 MATIC
|
0x7aa6...0fc274
|
0xb6ea...c2b52a
|
-
18.901711102268203 MATIC
|
0x7aa6...0fc274
|
0xf02f...4614ee
|
+
18.901711102268203 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.